Website readiness profile · Snapshot 23 October 2026
bt.no
bt.no's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 85/100
- Ahead of
- 97%
- Practices observed
- 25/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: bt.no. Thin bar: News & Media peer median.
Enable
92/100
Peers 89
Harden
74/100
Peers 56
Accelerate
100/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for bt.no
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.
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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
35% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
71% of News & Media peers do this.
Priority 3 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
66% of News & Media peers do this.
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for bt.no, so any public certificate authority may issue for it.
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.
13% of News & Media peers do this.
What bt.no already does well
Practices fewer than half of News & Media peers use.
- security.txt publishedsecurity.txt with a contact found.6.2% of peers
- Referrer-Policy setReferrer-Policy present.22% of peers
- Content Security Policy presentContent-Security-Policy present.29% of peers
What we saw
- Homepage checked
- https://www.bt.no/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-04
- CDN or edge
- Amazon CloudFront
- Platform or framework
- Astro
- DNS operators
- Amazon Route 53
- HSTS
- max-age 183 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 412 KB, br
- Images on homepage
- 25 (jpg 16, png 9, svg 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 6
Observed 25
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- 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
- Page language declared
- At most one redirect to the homepage
Own bt.no?
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: bt.no. This profile covers configuration only.