Skip to main content

Security report for reformedcatholicchurch.org

403 Forbidden · Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

46/100

Risk levelHigh

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

The website for reformedcatholicchurch.org is currently inaccessible, returning a 403 Forbidden error page with minimal HTML content. This indicates that access is blocked, likely by Cloudflare security mechanisms, as supported by the DNS records pointing to Cloudflare nameservers. Due to the lack of accessible content, no business description, contact information, or user engagement features are available for analysis. The site does not have a valid SSL/TLS certificate, and no HTTPS support is detected, which severely impacts security and trustworthiness. From a technical perspective, the infrastructure uses Cloudflare CDN and Hostinger mail servers, but the absence of SSL and modern TLS protocols, as well as missing security headers, indicates poor security hygiene. Performance is slow with minimal resources loaded, and no SEO or accessibility features are present. The WHOIS data shows the domain is registered and consistent with the domain name but provides no further business legitimacy signals. Security posture is weak due to lack of HTTPS, no HSTS, and no security headers. No privacy or cookie policies are found, and no contact or incident response information is available. Overall, the website is not operational for public users, which poses a critical risk for trust and business credibility. Strategic improvements are necessary to enable secure access, provide meaningful content, and comply with privacy and security best practices. Given the current state, the overall risk is high, and the website should prioritize resolving access issues, implementing HTTPS, and publishing essential policies and contact information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 reformedcatholicchurch.org

This scan found 16 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. See sample alerts.

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
0
Security headers
20
Email security
50
DNS health
90
Network security
100
GDPR outside view
15
Average
46

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

Due to the website being inaccessible and lacking content, no meaningful business intelligence can be derived. The domain name suggests a religious organization, but no information about market positioning, services, or business model is available. The absence of contact details, social media, or partner links further limits insights into operations or partnerships. The domain is registered and hosted via Cloudflare and Hostinger, indicating some level of infrastructure investment, but the lack of accessible content suggests the site may be under maintenance, restricted, or improperly configured.

Security posture

The security posture is currently poor. The site lacks a valid SSL certificate and does not support any TLS protocols, exposing users to insecure connections if accessed via HTTP. No security headers such as HSTS, CSP, or X-Frame-Options are present, increasing risk of common web attacks. The DNS setup uses Cloudflare nameservers, which can provide security benefits, but the 403 Forbidden response suggests restrictive access controls or misconfiguration. No incident response or vulnerability disclosure information is available, indicating low maturity in security governance. Immediate remediation is required to enable HTTPS, configure security headers, and provide transparency on security policies.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Configure and enable modern TLS protocols (TLS 1.2 or TLS 1.3) and disable insecure protocols.
  3. Implement security headers including HSTS with preload, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Review and adjust Cloudflare or server firewall settings to allow legitimate user access and avoid 403 Forbidden errors.
  5. Publish privacy policy, cookie policy, terms of service, and contact information to improve compliance and user trust.
Technical notes

Notes

The website is hosted behind Cloudflare CDN with multiple IPv4 and IPv6 addresses. DNS records include MX entries pointing to Hostinger mail servers, indicating email hosting setup. However, the SSL configuration is invalid or missing, with no TLS protocols enabled, resulting in no HTTPS support. The site loads only 2 resources with zero page size and a slow load time of over 7 seconds, indicating minimal or blocked content delivery. No CMS or frameworks are detectable from the HTML. The site is not optimized for SEO or accessibility, and no analytics or tracking scripts are present. The overall technical implementation is minimal and requires significant modernization and security hardening.
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 reformedcatholicchurch.org. 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 reformedcatholicchurch.org.

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.