No — beat-tokyo.ink is IPv4 only.

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

IPv6 readiness

The website has no IPv6.

Website over IPv6 beat-tokyo.ink has no AAAA record.	no
www over IPv6 www.beat-tokyo.ink has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:4402::ac40:94f9 answers · 443✓ 2a06:98c1:310d::6812:2707 answers · 443	yes
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record.	no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns2.xdomain.ne.jp ✗ns1.xdomain.ne.jp ✗ns3.xdomain.ne.jp ✗	no

What's keeping beat-tokyo.ink from an A

Give beat-tokyo.ink 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
Your domain's mail goes to its own address, which has no AAAA record.
Nameservers without IPv6
ns2.xdomain.ne.jp, ns1.xdomain.ne.jp, ns3.xdomain.ne.jp 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

beat-tokyo.ink IPv4 only

A (IPv4)	204.69.207.1
AAAA (IPv6)	none

www.beat-tokyo.ink Has IPv6

Alias of	sites.figma.net → wildcard.figma.net.cdn.cloudflare.net
A (IPv4)	104.18.39.7 172.64.148.249
AAAA (IPv6)	2606:4700:4402::ac40:94f9 2a06:98c1:310d::6812:2707

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: beat-tokyo.ink
Measured 2026-11-10 23:51:35 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    204.69.207.1
AAAA (IPv6): none
www AAAA:    2606:4700:4402::ac40:94f9, 2a06:98c1:310d::6812:2707

Readiness grade D: The website has no IPv6.
- Website over IPv6: beat-tokyo.ink has no AAAA record.
- www over IPv6: www.beat-tokyo.ink has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:4402::ac40:94f9: answers (TCP 443)
    2a06:98c1:310d::6812:2707: answers (TCP 443)
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has no 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/8YBLab55CC

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

Checked 2026-11-10 23:51:35 UTC. Full DNS report: dns.pizza/domain/beat-tokyo.ink · Age, certificate and blocklists: how.is/beat-tokyo.ink · JSON: /api/v1/beat-tokyo.ink