Skip to content
https://vatican.va

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
4
PASS
2
INFO
1
Probed from Sao Paulo, Brazil
200 OK
Checks
9
2 PASS 4 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.vatican.va/
200https://vatican.va/

Inconsistent — duplicate content risk

HTTP → HTTPS

http://vatican.va/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 39 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 39 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: * 
Crawl-delay: 2
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 870 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
217 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
214 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
222 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
871 ms
Total Time Total request time from DNS lookup through full response.
871 ms

Connection waterfall

DNS Lookup 217 ms TCP Connect 214 ms TLS Handshake 222 ms Server Processing 217 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
169 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

169
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 215 ms lookup
PASS
1 A records, 215 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.152.70.106
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: a.nic.va, c.nic.va, seth.namex.it, osiris.namex.it, b.nic.va
Info::
4 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (215 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 215 ms
A185.152.70.106
AAAA—
CNAME—
NSa.nic.va, c.nic.va, seth.namex.it, osiris.namex.it, b.nic.va
MX
10 mx11-new.vatican.va
10 mx12-new.vatican.va
30 mx20.vatican.va
30 mx21.vatican.va
TXT
google-site-verification=xJIGtooD1R7HCcYnGpEnQJbesRSBdJmzNZX0WLDIMII
SPF v=spf1 ip4:212.77.4.23 ip4:212.77.4.24 ip4:212.77.4.25 ip4:212.77.4.26 ~all
qZudITCslr0iehQZGvmCMAudIoMx0B6R5qAN4D3hPKw=
knowbe4-site-verification=f882cc0348b28c65c426d5e17921e866
globalsign-domain-verification=-gCC2DQXHa6oHAH2EjWC1H9VSKsrE2Gi4P5ejspYmK
CAALookup not available with standard resolver
Resolved in 215 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://vatican.va

https://vatican.va

862 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vatican.va200862 msHTTP/1.1Apache
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback