Yes — xn--hos.tokyo has IPv6.

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

B
IPv6 readiness
Works over IPv6, with one gap: its nameservers lack IPv6.
Website over IPv6
xn--hos.tokyo has an AAAA record and answers on it.
✓ 2400:8500:1301:162::24:1 answers · 443
yes
www over IPv6
www.xn--hos.tokyo has an AAAA record and answers on it.
✓ 2400:8500:1301:162::24:1 answers · 443
yes
Mail servers (MX) have IPv6
Every mail server has an AAAA record.
xn--hos.tokyo ✓
yes
Nameservers have IPv6
No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.
ns2.value-domain.com ✗ns1.value-domain.com ✗
no
HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 200.
https://xn--hos.tokyo/ via 2400:8500:1301:162::24:1 → 200
works
 Which outside scripts, fonts, payments or chat xn--hos.tokyo loads from have no IPv6.
 Load xn--hos.tokyo over IPv6 from up to six other places — a second opinion.

What's keeping xn--hos.tokyo from an A

  1. Nameservers without IPv6
    ns2.value-domain.com, ns1.value-domain.com all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

xn--hos.tokyo  Has IPv6

A (IPv4)163.44.176.24
AAAA (IPv6)2400:8500:1301:162::24:1

www.xn--hos.tokyo  Has IPv6

A (IPv4)163.44.176.24
AAAA (IPv6)2400:8500:1301:162::24:1

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

 Permanent link: aaaa.bot/r/cVRGW-PH2f · How we measure

Checked 2026-11-14 01:51:16 UTC. Full DNS report: dns.pizza/domain/xn--hos.tokyo · Age, certificate and blocklists: how.is/xn--hos.tokyo · JSON: /api/v1/xn--hos.tokyo