Skip to main content

Security report for pacjenci.pro

Non-profit · Poland

High risk. 9 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

0–100, higher is better. How it is calculated

The website pacjenci.pro represents a Polish non-profit foundation focused on patient support. The site uses WordPress with the Divi theme and is optimized with Yoast SEO, indicating a moderate level of digital maturity. The content is primarily in Polish and targets patients and healthcare beneficiaries. Technically, the site is moderately optimized for performance and mobile use but lacks advanced security headers and visible privacy compliance mechanisms. The WHOIS data is unavailable due to privacy protection, which is common for non-profit organizations but reduces transparency. Overall, the security posture is basic with room for improvement in privacy and security best practices. Strategic recommendations include implementing comprehensive privacy and cookie policies, enhancing security headers, and providing clear contact and incident response information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

9 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

Need hands-on remediation? Email guard@offseq.com

Keep watching pacjenci.pro

This scan found 25 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
72
Security headers
20
Email security
70
DNS health
70
Network security
0
GDPR outside view
65
Average
50
After the cap
49

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet · found on this site
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention pacjenci.pro, from OffSeq Breach.

No leaked records found

Breach holds no records for pacjenci.pro right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Pacjenci.pro operates as a non-profit foundation serving patients in Poland. The business model is centered on providing support services, likely including advocacy, information, and assistance. The website's market position is not explicitly stated, but the use of professional themes and SEO tools suggests an intent to reach a broad patient audience. No direct partnerships or subsidiaries are identified. The absence of detailed business information and contact data limits deeper business intelligence insights. Growth indicators and revenue streams are not discernible from the website content. The foundation appears to maintain a consistent brand presence with good content relevance and user experience.

Security posture

The website currently exhibits a basic security posture. HTTPS is presumably enabled, but no explicit security headers such as Content-Security-Policy or Strict-Transport-Security are detected. There is no evidence of exposed sensitive data or vulnerable libraries in the provided content. The lack of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. Incident response and security contact information are not present, which could hinder timely reporting and mitigation of security incidents. Overall, the site would benefit from enhanced security controls, regular updates, and transparent privacy practices to strengthen its security maturity and compliance.

Recommendations

  1. Implement comprehensive privacy and cookie policies to ensure GDPR compliance.
  2. Add and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide clear contact information and establish an incident response contact channel.
  4. Regularly update WordPress core, themes, and plugins to mitigate vulnerabilities.
  5. Enhance transparency by publishing WHOIS registrant information if possible or providing organizational details on the site.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Fundacja providing support for patients, likely in healthcare or social support domain.
Key services
patient support, foundation activities
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, CSS, HTML5
Frameworks
Divi Theme
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is accessible and not blocked by WAF or security mechanisms.
  2. WHOIS data is unavailable due to privacy protection or malformed request.
  3. No explicit privacy, cookie, or terms of service policies found on the homepage content.
  4. No contact emails or phone numbers explicitly found in the visible content.
  5. Website uses WordPress with Divi theme and includes Yoast SEO plugin.
  6. No analytics or advertising scripts detected in the provided HTML snippet.
  7. Content is in Polish language targeting patients and healthcare support.
  8. No security headers detected in the provided data; SSL is present but configuration details unknown.
  9. No forms detected in the provided HTML snippet.
  10. No social media links explicitly found in the provided content.
Technical notes

Notes

The website is built on WordPress using the Divi theme, a popular and flexible CMS framework. It includes the Yoast SEO plugin, indicating attention to search engine optimization. The site uses standard web technologies including JavaScript, CSS, and HTML5. Performance appears moderate with no explicit indicators of slow loading or technical debt in the provided content. Mobile optimization is good, supported by responsive design elements. Accessibility features are basic but present. No advanced frameworks or hosting provider details are identified. The site lacks visible analytics or marketing tools, suggesting minimal tracking or advertising integration.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with pacjenci.pro. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review pacjenci.pro.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.