No — xn--delipicks-yz4h6hrwt359bu0j.tokyo is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

This is a saved measurement from 2026-10-31 02:20 UTC. Check xn--delipicks-yz4h6hrwt359bu0j.tokyo live now

IPv6 readiness

The website has no IPv6.

Website over IPv6 xn--delipicks-yz4h6hrwt359bu0j.tokyo has no AAAA record.	no
www over IPv6 www.xn--delipicks-yz4h6hrwt359bu0j.tokyo has no AAAA record.	no
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. xn--delipicks-yz4h6hrwt359bu0j.tokyo ✗	no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns1.value-domain.com ✗ns2.value-domain.com ✗	no

What's keeping xn--delipicks-yz4h6hrwt359bu0j.tokyo from an A

Give xn--delipicks-yz4h6hrwt359bu0j.tokyo and www.xn--delipicks-yz4h6hrwt359bu0j.tokyo an IPv6 address
Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
Mail servers without IPv6
xn--delipicks-yz4h6hrwt359bu0j.tokyo has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.
Nameservers without IPv6
ns1.value-domain.com, ns2.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--delipicks-yz4h6hrwt359bu0j.tokyo IPv4 only

A (IPv4)	202.172.28.169
AAAA (IPv6)	none

www.xn--delipicks-yz4h6hrwt359bu0j.tokyo IPv4 only

A (IPv4)	202.172.28.169
AAAA (IPv6)	none

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

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

IPv6 measurement: xn--delipicks-yz4h6hrwt359bu0j.tokyo
Measured 2026-10-31 02:20:05 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    202.172.28.169
AAAA (IPv6): none
www AAAA:    none

Readiness grade D: The website has no IPv6.
- Website over IPv6: xn--delipicks-yz4h6hrwt359bu0j.tokyo has no AAAA record.
- www over IPv6: www.xn--delipicks-yz4h6hrwt359bu0j.tokyo has no AAAA record.
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/S7QTVjloZH

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

Checked 2026-10-31 02:20:05 UTC. Full DNS report: dns.pizza/domain/xn--delipicks-yz4h6hrwt359bu0j.tokyo · JSON: /api/v1/xn--delipicks-yz4h6hrwt359bu0j.tokyo