Website readiness profile · Snapshot 23 October 2026
zerohedge.com
zerohedge.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 60/100
- Ahead of
- 20%
- Practices observed
- 17/31
- Popularity band
- Top 50K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: zerohedge.com. Thin bar: News & Media peer median.
Enable
56/100
Peers 89
Harden
37/100
Peers 56
Accelerate
100/100
Peers 68
Recover
100/100
Peers 11
Priority fixes for zerohedge.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://www.zerohedge.com/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
96% of News & Media peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
87% of News & Media peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.
On Next.js: Add the header in the headers() option of next.config.js for all routes.
35% of News & Media peers do this.
Priority 4 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
89% of News & Media peers do this.
What zerohedge.com already does well
Practices fewer than half of News & Media peers use.
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
- HTTP/3 advertisedHTTP/3 advertised.36% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers
What we saw
- Homepage checked
- https://www.zerohedge.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-28
- CDN or edge
- Google edge
- Platform or framework
- Next.js
- DNS operators
- 4 self-run or other nameserver domains
- DMARC policy
- p=reject
- Homepage HTML
- 173 KB, gzip
- Images on homepage
- 41 (jpg 211, png 173, webp 24, svg 13)
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 14
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Social preview image set
Observed 17
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DMARC policy enforces quarantine or reject
- 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
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own zerohedge.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: zerohedge.com. This profile covers configuration only.