Skip to main content

Security report for vatican.va

Vatican · Government · Vatican City

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

Security score

48/100

Risk levelHigh

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

The Vatican website serves as the official online presence of the Vatican City State and the central governing body of the Roman Catholic Church. It provides multilingual content aimed at a global audience interested in religious, cultural, and official Vatican communications. The site uses Adobe Granite CMS and the Foundation framework, with Google Tag Manager integrated for analytics. However, the website lacks a valid SSL certificate, which critically undermines its security posture despite the presence of several security headers. No privacy or cookie policies are found on the landing page, and contact information is minimal, limited to a DMARC reporting email. The domain registration is consistent with the Vatican entity, indicating legitimacy. Overall, the site demonstrates basic content and technical implementation but requires significant improvements in security and privacy compliance to meet modern standards.

Scanned

This is an earlier scan of vatican.va. View the latest report

NIS2 and GDPR posture

GDPR outside view
0/ 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

7 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

    • 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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  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 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 vatican.va

This scan found 17 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
60
Email security
50
DNS health
80
Network security
100
GDPR outside view
0
Average
48

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

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 vatican.va, from OffSeq Breach.

Total records
342
Employees
0
Customers
301
Third parties
41
Weak passwords
21%

11 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for vatican.va.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

The Vatican operates as a sovereign government and religious institution with a unique market position. Its website functions primarily as an information dissemination platform rather than a commercial entity. The business model focuses on providing official communications and cultural content to a worldwide audience. The lack of detailed business or contact information on the site aligns with its governmental and religious nature. The use of multiple MX servers and DNS records indicates a well-managed email infrastructure. The site’s partnership ecosystem is minimal, with no visible external business partners or subsidiaries linked from the site.

Security posture

The current security posture is weak due to the absence of a valid SSL certificate and lack of modern TLS protocol support, which exposes users to potential interception risks. While security headers such as HSTS, X-Content-Type-Options, X-Frame-Options, and X-XSS-Protection are implemented, they cannot compensate for the fundamental lack of HTTPS. No vulnerability disclosure or incident response information is provided, and no security.txt file is present. The site’s DNS configuration includes SPF and DMARC records, which help protect email integrity. Overall, the site is vulnerable to man-in-the-middle attacks and does not meet basic security best practices.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate immediately to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and configure strong cipher suites to secure communications.
  3. Publish clear privacy and cookie policies with GDPR compliance statements to improve transparency and legal compliance.
  4. Add contact information and security incident response details, including a security.txt file, to enhance trust and preparedness.
  5. Regularly audit and update security headers and implement OCSP stapling and session resumption to improve SSL performance and security.
Technical notes

Notes

The website is built on Adobe Granite CMS (AEM) and uses the Foundation CSS framework along with jQuery libraries. Google Tag Manager is integrated for analytics and tracking. The site redirects users based on browser language preferences to localized content pages. DNS records are well configured with multiple MX servers and SPF/DMARC policies, but DNSSEC and CAA are not enabled. The hosting environment appears to be Microsoft Azure. Performance metrics are unavailable, but the site uses minified CSS and JS resources. Mobile optimization and accessibility cannot be fully assessed from the provided data. The lack of SSL/TLS is a critical technical deficiency that impacts security and user trust.
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

Earlier scans of this domain

  1. 73/100 −3Medium30 findingsView report
  2. 76/100 +18Low27 findingsView report
  3. 58/100Medium25 findingsView report
Reviews of this site

Share your experience with vatican.va. 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 vatican.va.

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.