Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

301 Moved Permanently

Checks

4 PASS 4 REVIEW

Redirect Chain

2 redirect(s), 907 ms total

REVIEW

2 redirect(s), 907 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

HTTP to HTTPS redirect present

WWW normalization redirect

2-hop chain could be reduced to 1 hop

Redirect directly from https://ipcc.ch to https://www.ipcc.ch/

Redirect overhead: 907 ms total

Got: 907 ms

https://ipcc.ch

104 ms · HTTP/1.1

301

http://www.ipcc.ch/

82 ms · HTTP/1.1

301

https://www.ipcc.ch/

722 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://ipcc.ch	301	104 ms	HTTP/1.1	cloudflare
2	http://www.ipcc.ch/	301	82 ms	HTTP/1.1	cloudflare
3	https://www.ipcc.ch/	200	722 ms	HTTP/1.1	cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://ipcc.ch to https://www.ipcc.ch/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

Crawlability

robots.txt present, no sitemap

REVIEW

robots.txt present, no sitemap

robots.txt is present

Got: 77 bytes

No sitemap.xml found

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

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 77 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /site/wp-admin/
Allow: /site/wp-admin/admin-ajax.php

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ipcc.ch/

200https://ipcc.ch/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ipcc.ch/ → https://ipcc.ch/

Consistent

TLS Certificate Expiry & Recommendations

53 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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

2 A records, 58 ms lookup

PASS

2 A records, 58 ms lookup

Resolves to 2 IPv4 address(es)

Got: 172.66.137.194, 172.66.135.149

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:10::ac42:8795, 2606:4700:10::ac42:89c2

2 nameserver(s) configured

Got: asa.ns.cloudflare.com, guss.ns.cloudflare.com

1 mail exchanger(s) configured

CAA records not checked

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

SPF record present in TXT

DNS resolution time: 58 ms

Got: 58 ms

A	172.66.137.194, 172.66.135.149
AAAA	2606:4700:10::ac42:8795, 2606:4700:10::ac42:89c2
CNAME	—
NS	asa.ns.cloudflare.com, guss.ns.cloudflare.com
MX	0 ipcc-ch.mail.protection.outlook.com
TXT	ZOOM_verify_mm-gEiZoTD6yvS1mtHDPEg SPF v=spf1 include:spf.protection.outlook.com -all MS=ms97349036
CAA	Lookup not available with standard resolver

Resolved in 58 ms

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.

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2606:4700:10::ac42:8795, 2606:4700:10::ac42:89c2

Got: 17 ms connect

IPv6 Ready

AAAA Records 2606:4700:10::ac42:8795, 2606:4700:10::ac42:89c2 Connection Reachable (17 ms)

A+

HTTP Probe Timing

Total 141 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

46 ms

TCP Connect

17 ms

TLS Handshake

23 ms

Time to First Byte

141 ms

Total Time

141 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 56 ms Content Transfer 0 ms

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: 9efed8739eeb592b-CDG

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9efed8739eeb592b-CDG

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.