Website readiness profile · Snapshot 23 October 2026
cnnbrasil.com.br
cnnbrasil.com.br's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 69/100
- Ahead of
- 54%
- Practices observed
- 20/31
- Popularity band
- Top 1K
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: cnnbrasil.com.br. Thin bar: News & Media peer median.
Enable
100/100
Peers 89
Harden
48/100
Peers 56
Accelerate
78/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for cnnbrasil.com.br
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.
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. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for cnnbrasil.com.br was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
37% of News & Media peers do this.
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 1 external script without async or defer.
What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.
On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.
42% of News & Media peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
On Next.js: Add it in next.config.js headers().
42% of News & Media peers do this.
What cnnbrasil.com.br already does well
Practices fewer than half of News & Media peers use.
- X-Content-Type-Options: nosniffnosniff header present.42% of peers
- Modern image formats in useWebP or AVIF images detected.44% of peers
What we saw
- Homepage checked
- https://www.cnnbrasil.com.br/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-30
- Platform or framework
- WordPress, Next.js
- DNS operators
- Azure DNS
- DMARC policy
- p=none
- Homepage HTML
- 1,000 KB, br
- Images on homepage
- 144 (jpg 138, png 81, webp 12, svg 4)
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 11
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- No render-blocking scripts in <head>
- Nameservers spread across providers
Observed 20
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- 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 cnnbrasil.com.br?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: cnnbrasil.com.br. This profile covers configuration only.