Website readiness profile · Snapshot 23 October 2026
whitehouse.gov
whitehouse.gov's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.
- Readiness index
- 90/100
- Ahead of
- >99%
- Practices observed
- 27/31
- Popularity band
- Top 50K
Government Services median 53
of measured Government Services sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: whitehouse.gov. Thin bar: Government Services peer median.
Enable
100/100
Peers 59
Harden
88/100
Peers 59
Accelerate
90/100
Peers 41
Recover
0/100
Peers 25
Priority fixes for whitehouse.gov
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for whitehouse.gov, so any public certificate authority may issue for it.
Why it matters: CAA records tell certificate authorities which of them may issue certificates for your domain, which narrows the chance of a mistaken or fraudulent certificate.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
17% of Government Services peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.
Priority 2 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
11% of Government Services peers do this.
Priority 3 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
8% of Government Services peers do this.
Priority 4 · Recover
Nameservers spread across providers
Observed: All nameservers for whitehouse.gov belong to Cloudflare.
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.
25% of Government Services peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What whitehouse.gov already does well
Practices fewer than half of Government Services peers use.
- Modern image formats in useWebP or AVIF images detected.15% of peers
- Structured data presentJSON-LD structured data found.15% of peers
- DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
What we saw
- Homepage checked
- https://www.whitehouse.gov/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2027-01-03
- Platform or framework
- WordPress
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 292 KB, br
- Images on homepage
- 23 (jpg 34, png 16, webp 2, gif 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 4
Observed 27
- 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
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- 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 whitehouse.gov?
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: whitehouse.gov. This profile covers configuration only.