Website readiness profile · Snapshot 23 October 2026
cloudflare.com
cloudflare.com's public homepage, certificate and DNS checked against 31 practices and compared with 40 Web Hosting & Infrastructure sites.
- Readiness index
- 99/100
- Ahead of
- 98%
- Practices observed
- 30/31
- Popularity band
- Top 10K
Web Hosting & Infrastructure median 74
of measured Web Hosting & Infrastructure sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: cloudflare.com. Thin bar: Web Hosting & Infrastructure peer median.
Enable
100/100
Peers 83
Harden
100/100
Peers 67
Accelerate
100/100
Peers 70
Recover
0/100
Peers 18
Priority fixes for cloudflare.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Recover
Nameservers spread across providers
Observed: All nameservers for cloudflare.com belong to a single operator.
Why it matters: If every nameserver belongs to one provider, a problem at that provider can stop your domain resolving. RFC 2182 (BCP 16) recommends spreading secondary servers across diverse networks.
What to do: Treat this as an advanced step. Add a secondary DNS provider through zone transfers or a multi-provider setup, then test changes carefully, since both providers must stay in sync.
On Cloudflare: Cloudflare supports zone transfers for primary or secondary DNS setups on eligible plans.
18% of Web Hosting & Infrastructure peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What cloudflare.com already does well
Practices fewer than half of Web Hosting & Infrastructure peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.28% of peers
- HTTP/3 advertisedHTTP/3 advertised.33% of peers
- Referrer-Policy setReferrer-Policy present.33% of peers
What we saw
- Homepage checked
- https://www.cloudflare.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-10
- CDN or edge
- Cloudflare
- Platform or framework
- Astro
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 1,303 KB, br
- Images on homepage
- 68 (svg 64, png 3, avif 1)
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Not observed 1
Observed 30
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own cloudflare.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: cloudflare.com. This profile covers configuration only.