Website readiness profile · Snapshot 23 October 2026

bloomberg.com

bloomberg.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index: 90/100
Ahead of: >99%
Practices observed: 27/31
Popularity band: Top 5K

Measured 2026-10-23 11:26:02 UTC from one location. How we measure

Readiness by lane

Green: bloomberg.com. Thin bar: News & Media peer median.

Enable

95/100

Peers 89

Harden

91/100

Peers 56

Accelerate

85/100

Peers 68

Recover

100/100

Peers 11

Priority fixes for bloomberg.com

Ordered by impact and by how common each practice is among peers.

Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 hours, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
60% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: Browser Caching Guide for Website Owners
Priority 2 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from DigiCert Inc had a 389-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.
Guide: HTTPS and TLS Guide for Website Owners
Priority 3 · Enable
Reachable over IPv6
Observed: No IPv6 (AAAA) address was published for www.bloomberg.com.
What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.
51% of News & Media peers do this.
Guide: How to Evaluate Web Hosting Performance
Priority 4 · Harden
DNSSEC signed
Observed: No DS record was found for bloomberg.com at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
6.1% of News & Media peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What bloomberg.com already does well

Practices fewer than half of News & Media peers use.

security.txt publishedsecurity.txt with a contact found.6.2% of peers
Nameservers spread across providersNameservers spread across NS1 and Vercara UltraDNS.11% of peers
CAA records limit who can issue certificatesCAA limits issuance to amazon.com, digicert.com.13% of peers

What we saw

Homepage checked: https://www.bloomberg.com/
Homepage response: HTTP 200
TLS: TLSv1.3, HTTP/2
Certificate: DigiCert, 389-day validity, expiring 2027-02-14
Platform or framework: Next.js
DNS operators: NS1, Vercara UltraDNS
HSTS: max-age 365 days
DMARC policy: p=reject
Homepage HTML: 8,233 KB, br
Images on homepage: 107 (webp 352, jpg 94, png 25)

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.

Next.js readiness playbook NS1 (dns operator)Vercara UltraDNS (dns operator)DigiCert (certificate authority)

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
CAA records limit who can issue certificates
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
Modern image formats in use
Offscreen images lazy-loaded
No render-blocking scripts in <head>
robots.txt published
XML sitemap discoverable
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
Nameservers spread across providers

Own bloomberg.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Re-check bloomberg.com now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: bloomberg.com. This profile covers configuration only.

Compare with other News & Media sites

News & Media readiness benchmark