Website readiness profile · Snapshot 23 October 2026
nikkei.com
nikkei.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 92/100
- Ahead of
- >99%
- Practices observed
- 27/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: nikkei.com. Thin bar: News & Media peer median.
Enable
100/100
Peers 89
Harden
85/100
Peers 56
Accelerate
100/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for nikkei.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from GlobalSign nv-sa had a 396-day validity period, longer than the 100-day maximum that applies from March 2027.
Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.
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. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for nikkei.com, 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.
Priority 3 · Harden
DNSSEC signed
Observed: No DS record was found for nikkei.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.
On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.
6.1% of News & Media peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
Priority 4 · Recover
Nameservers spread across providers
Observed: All nameservers for nikkei.com belong to Amazon Route 53.
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.
11% of News & Media peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What nikkei.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
- 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.nikkei.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GlobalSign, 396-day validity, expiring 2027-01-16
- DNS operators
- Amazon Route 53
- HSTS
- max-age 730 days
- DMARC policy
- p=quarantine
- Homepage HTML
- 728 KB, br
- Images on homepage
- 233 (jpg 635, png 100, svg 83)
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
- 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
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own nikkei.com?
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: nikkei.com. This profile covers configuration only.