Yes — tanopay.app has IPv6.

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

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 tanopay.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:4d:59f8:3a85:8c81:c816:5fce answers · 443✓ 2a02:4780:4b:ef42:15f1:2ba6:7bda:befd answers · 443	yes
www over IPv6 www.tanopay.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:4d:e273:ada2:bb:e7a:d834 answers · 443✓ 2a02:4780:4a:85b8:fde0:7ea:4fcf:b7e7 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. eforward1.registrar-servers.com ✗eforward2.registrar-servers.com ✗eforward3.registrar-servers.com ✗eforward4.registrar-servers.com ✗eforward5.registrar-servers.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns1.registrar-servers.com ✓dns2.registrar-servers.com ✓	yes

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

https://tanopay.app/ via 2a02:4780:4d:59f8:3a85:8c81:c816:5fce → 200

works

What's keeping tanopay.app from an A

Mail servers without IPv6
eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

tanopay.app Has IPv6

A (IPv4)	88.223.87.224 147.79.72.236
AAAA (IPv6)	2a02:4780:4d:59f8:3a85:8c81:c816:5fce 2a02:4780:4b:ef42:15f1:2ba6:7bda:befd

www.tanopay.app Has IPv6

Alias of	www.tanopay.app.cdn.hstgr.net
A (IPv4)	84.32.84.250 2.57.91.179
AAAA (IPv6)	2a02:4780:4d:e273:ada2:bb:e7a:d834 2a02:4780:4a:85b8:fde0:7ea:4fcf:b7e7

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: tanopay.app
Measured 2026-10-31 00:25:30 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    88.223.87.224, 147.79.72.236
AAAA (IPv6): 2a02:4780:4d:59f8:3a85:8c81:c816:5fce, 2a02:4780:4b:ef42:15f1:2ba6:7bda:befd
www AAAA:    2a02:4780:4d:e273:ada2:bb:e7a:d834, 2a02:4780:4a:85b8:fde0:7ea:4fcf:b7e7

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: tanopay.app has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:4d:59f8:3a85:8c81:c816:5fce: answers (TCP 443)
    2a02:4780:4b:ef42:15f1:2ba6:7bda:befd: answers (TCP 443)
- www over IPv6: www.tanopay.app has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:4d:e273:ada2:bb:e7a:d834: answers (TCP 443)
    2a02:4780:4a:85b8:fde0:7ea:4fcf:b7e7: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: 2 of 2 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: HTTP 200.
    https://tanopay.app/ via 2a02:4780:4d:59f8:3a85:8c81:c816:5fce -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/Bby27kNOOL

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

Checked 2026-10-31 00:25:30 UTC. Full DNS report: dns.pizza/domain/tanopay.app · JSON: /api/v1/tanopay.app