Yes — nikkei.com has IPv6.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

This is a saved measurement from 2026-10-31 04:04 UTC. Check nikkei.com live now

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 nikkei.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2600:9000:a717:b171:7f68:c620:6880:1f5a answers · 443✓ 2600:9000:a615:e7f2:2ea1:cf50:5844:399f answers · 443	yes
www over IPv6 www.nikkei.com has 4 IPv6 addresses and answers on every one we tested. ✓ 2a04:4e42::311 answers · 443✓ 2a04:4e42:200::311 answers · 443✓ 2a04:4e42:400::311 answers · 443✓ 2a04:4e42:600::311 answers · 443	yes
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns-1261.awsdns-29.org ✓ns-1974.awsdns-54.co.uk ✓ns-59.awsdns-07.com ✓ns-699.awsdns-23.net ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.

https://nikkei.com/ via 2600:9000:a717:b171:7f68:c620:6880:1f5a → 302https://www.nikkei.com/ via 2a04:4e42::311 → 200

works

Nothing keeping you from an A

Nothing to fix
Show it off: add the badge to your README.
[![IPv6](https://aaaa.bot/badge/nikkei.com.svg)](https://aaaa.bot/nikkei.com)

Check again

nikkei.com Has IPv6

A (IPv4)	52.223.0.196 35.71.146.174
AAAA (IPv6)	2600:9000:a717:b171:7f68:c620:6880:1f5a 2600:9000:a615:e7f2:2ea1:cf50:5844:399f

www.nikkei.com Has IPv6

Alias of	www-nikkei-com.n8s.jp → dualstack.m.sni.global.fastly.net
A (IPv4)	151.101.1.55 151.101.65.55 151.101.129.55 151.101.193.55
AAAA (IPv6)	2a04:4e42::311 2a04:4e42:200::311 2a04:4e42:400::311 2a04:4e42:600::311

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: nikkei.com
Measured 2026-10-31 04:04:31 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    52.223.0.196, 35.71.146.174
AAAA (IPv6): 2600:9000:a717:b171:7f68:c620:6880:1f5a, 2600:9000:a615:e7f2:2ea1:cf50:5844:399f
www AAAA:    2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:400::311, 2a04:4e42:600::311

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: nikkei.com has 2 IPv6 addresses and answers on every one we tested.
    2600:9000:a717:b171:7f68:c620:6880:1f5a: answers (TCP 443)
    2600:9000:a615:e7f2:2ea1:cf50:5844:399f: answers (TCP 443)
- www over IPv6: www.nikkei.com has 4 IPv6 addresses and answers on every one we tested.
    2a04:4e42::311: answers (TCP 443)
    2a04:4e42:200::311: answers (TCP 443)
    2a04:4e42:400::311: answers (TCP 443)
    2a04:4e42:600::311: answers (TCP 443)
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.
- Nameservers have IPv6: 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
    https://nikkei.com/ via 2600:9000:a717:b171:7f68:c620:6880:1f5a -> HTTP 302, certificate: valid
    https://www.nikkei.com/ via 2a04:4e42::311 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/FisUzJv6fM

Permanent link: aaaa.bot/r/FisUzJv6fM · How we measure

Checked 2026-10-31 04:04:31 UTC. Full DNS report: dns.pizza/domain/nikkei.com · JSON: /api/v1/nikkei.com