Skip to main content

Security report for orthodox.pl

Polski Autokefaliczny Kościół Prawosławny · Government · Poland

High risk. 8 critical or high findings in GDPR outside view, Security headers and 2 other checks.

Security score

47/100

Risk levelHigh

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

The website represents the official online presence of the Polish Autocephalous Orthodox Church, a religious non-profit organization serving the Orthodox Christian community in Poland. It provides news, administrative information, media resources, and community services. The site is well-structured with clear navigation and consistent branding, targeting members and followers of the church as well as the general public interested in Orthodox Christianity in Poland. Technically, the site is built on WordPress with common plugins for event management, media display, and cookie consent, reflecting a moderate level of digital maturity. Security posture is adequate with HTTPS enforced and cookie consent implemented, but lacks advanced security headers and analytics integration. The absence of WHOIS data from the Polish registry reduces transparency and trustworthiness, although the website content and organization branding strongly indicate legitimacy. Overall, the site is safe, professional, and compliant with basic privacy standards, but could improve in security best practices and privacy policy transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

  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 orthodox.pl

This scan found 26 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
62
Security headers
15
Email security
70
DNS health
75
Network security
20
GDPR outside view
40
Average
47

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
  • 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

Technical appendix

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

Business context

Business profile

The Polish Autocephalous Orthodox Church holds a significant position as the official Orthodox religious institution in Poland, serving a medium-sized community. Its business model is non-profit and focused on religious, educational, and community services. The website supports this by providing detailed organizational information, news updates, and media content. The church's target audience includes clergy, faithful members, theological students, and the wider public interested in Orthodox Christianity. The site shows moderate digital engagement with event calendars and multimedia presentations. Partnerships appear limited to service providers such as the website creator. The lack of direct contact details and WHOIS transparency may limit some user trust and engagement opportunities.

Security posture

The website enforces HTTPS and includes a cookie consent mechanism aligned with GDPR requirements, indicating awareness of privacy and security compliance. However, it lacks visible security headers such as Content-Security-Policy, X-Frame-Options, and others that enhance protection against common web attacks. No analytics or tracking scripts are detected, reducing privacy risks but also limiting user behavior insights. No vulnerabilities or exposed sensitive data were found in the HTML content. The absence of a security.txt file or incident response contact information suggests limited formal vulnerability disclosure readiness. Overall, the security posture is moderate but could be strengthened by implementing recommended headers, formalizing incident response channels, and improving privacy policy transparency.

Recommendations

  1. Implement security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance web security.
  2. Publish a clear and comprehensive privacy policy and terms of service pages to improve transparency and compliance.
  3. Add a security.txt file to facilitate vulnerability disclosure and incident response communication.
  4. Enhance accessibility features to meet recognized standards and improve user experience for all visitors.
  5. Regularly audit and update WordPress plugins and themes to mitigate potential vulnerabilities and maintain performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Polski Autokefaliczny Kościół Prawosławny
Description
Official website of the Polish Autocephalous Orthodox Church providing news, administration info, media, and religious resources.
Key services
Religious news and announcements, Church administration information, Religious education and theological schooling, Media resources including publications, photos, and videos, Community and pastoral services
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, jQuery UI, RevSlider, Event Calendar WD, Lightbox Plus Colorbox, Captcha plugin, Cookie Law Info plugin, PanoPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Marketing tools
CookieYes Cookie Consent
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and navigation.
  2. No WHOIS data available from the Polish registry, which is unusual and reduces transparency.
  3. Cookie consent mechanism is implemented and GDPR-focused.
  4. No explicit privacy policy or terms of service pages found.
  5. No direct contact emails or phone numbers found in the HTML content.
  6. Website uses WordPress with common plugins for media and events.
  7. No security headers detected in the HTML source.
  8. No analytics scripts like Google Analytics detected.
  9. No advertising or tracking networks detected beyond cookie consent.
  10. Content is religious, safe, and targeted at general audiences.
Technical notes

Notes

The website is built on WordPress CMS using a variety of plugins such as RevSlider, Event Calendar WD, Lightbox Plus Colorbox, and Cookie Law Info for cookie consent management. The front-end uses jQuery and jQuery UI libraries. The site loads fonts from Google Fonts and includes custom scripts for slider and media presentation. Performance is moderate with no major blocking scripts detected. Mobile optimization is good with responsive design elements. SEO optimization is basic with meta tags present but no advanced structured data or Open Graph tags detected. Accessibility is basic with some ARIA roles but could be improved. Hosting provider details are not evident from the HTML content. Overall, the technical infrastructure is standard for a medium-sized WordPress site but could benefit from modernization and enhanced SEO and accessibility practices.
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 orthodox.pl. 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 orthodox.pl.

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.