Skip to content
https://www.nikkei.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
5 PASS 2 REVIEW 2 FIX
D
HTTP Probe Timing
Action
Total 2387 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
295 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
2 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.38 s
Total Time Total request time from DNS lookup through full response.
2.39 s

Connection waterfall

DNS Lookup 295 ms TCP Connect 0 ms TLS Handshake 2 ms Server Processing 2.09 s Content Transfer 2 ms
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
4 A records, 24 ms lookup
REVIEW
4 A records, 24 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.193.55, 151.101.1.55, 151.101.65.55, 151.101.129.55
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:600::311, 2a04:4e42:400::311
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www-nikkei-com.n8s.jp
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A151.101.193.55, 151.101.1.55, 151.101.65.55, 151.101.129.55
AAAA2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:600::311, 2a04:4e42:400::311
CNAMEwww-nikkei-com.n8s.jp
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 24 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
TLS Certificate Expiry & Recommendations
283 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

283
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.nikkei.com

https://www.nikkei.com

1695 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nikkei.com2001695 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:600::311, 2a04:4e42:400::311
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:600::311, 2a04:4e42:400::311 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 2149 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2149 B Sitemaps referenced 2 User-agents PerplexityBot, PiplBot, AI2Bot-Dolma, Claude-SearchBot, magpie-crawler, meta-externalfetcher, Google-CloudVertexBot, YouBot, SBIntuitions-SearchBot, Applebot-Extended, MJ12bot, img2dataset, anthropic-ai, omgili, ICC-Crawler, Diffbot, AmazonBot, cohere-training-data-crawler, SeekrBot, Webzio, cohere-ai, omgilibot, Claude-Web, Claude-User, FacebookBot, Scrapy, OpenindexSpider, GPTBot, ChatGPT-User, Perplexity-ai, Meta-ExternalAgent, Gensparkbot, *, Bytespider, DuckAssistBot, Timpibot, Webzio-extended, Google-Extended, ClaudeBot, Perplexity-User, OAI-SearchBot, AI2Bot, SBIntuitionsBot, CCBot Blocking No — crawling allowed
User-agent: *
Allow: /markets/kabu/stkcomp/$
Allow: /markets/kabu/gyoshucomp/$
Disallow: /.tools
Disallow: /markets/kabu/stkcomp/
Disallow: /markets/kabu/gyoshucomp/
Disallow: /.resources/k-components/rtoaster/

# If you want to use our data in machine learning, please contact us from the following url.
# ja:  https://nkbb.nikkei.co.jp/article/
# en:  https://nkbb.nikkei.co.jp/en/dataset/nikkei-news-articles

User-agent: CCBot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: cohere-ai
Disallow: /

User-Agent: omgili
Disallow: /

User-Agent: omgilibot
Disallow: /

User-Agent: ICC-Crawler
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Claude-SearchBot
Disallow: /

User-agent: Claude-User
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-ai
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: MJ12bot
Disallow: /

User-agent: PiplBot
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio
Disallow: /

User-agent: Webzio-extended
Disallow: /

User-agent: AmazonBot
Disallow: /

User-agent: cohere-training-data-crawler
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: meta-externalfetcher
Disallow: /

User-agent: Scrapy
Disallow: /

User-agent: DuckAssistBot
Disallow: /

User-agent: Google-CloudVertexBot
Disallow: /

User-agent: AI2Bot
Disallow: /

User-agent: AI2Bot-Dolma
Disallow: /

User-agent: img2dataset
Disallow: /

User-agent: YouBot
Disallow: /

User-agent: SeekrBot
Disallow: /

User-agent: OpenindexSpider
Disallow: /

User-agent: Gensparkbot
Disallow: /

User-agent: SBIntuitionsBot
Disallow: /

User-agent: SBIntuitions-SearchBot
Disallow: /

Sitemap: https://www.nikkei.com/sitemap.xml
Sitemap: https://www.nikkei.com/sitemaps/topics_sitemap_index.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.nikkei.com/
302https://nikkei.com/

Preferred variant: www

HTTP → HTTPS

301http://www.nikkei.com/ https://www.nikkei.com/

Consistent

A
Domain Intelligence
nikkei.com — via Japan Registry Services Co., Ltd., 31 years, 4 months old
PASS
nikkei.com — via Japan Registry Services Co., Ltd., 31 years, 4 months old
Warning::
Domain expires in 32 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 10, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Japan Registry Services Co., Ltd.
Domain expiry

EXPIRED

May 10, 2026

SSL certificate

283 days

Issued by GlobalSign nv-sa

Domain age

31 years, 4 months

Registered May 9, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:a615:e7f2:2ea1:cf50:5844:399f

Registrar

Japan Registry Services Co., Ltd.

Lock status unknown 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Japan Registry Services Co., Ltd.
Created May 9, 1995 (31 years, 4 months ago)
Expires May 10, 2026 (1 months)
Last Updated May 8, 2025
Name Servers i31dnsb0.nikkei.co.jp, ns00.vips.ne.jp, ns01.vips.ne.jp, robert.nikkei.co.jp, william.nikkei.co.jp
DNSSEC Not enabled
Hosting
IP Address 2600:9000:a615:e7f2:2ea1:cf50:5844:399f
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback