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:4a:d5a7:60ea:85b1:74b:60d4 answers · 443✓ 2a02:4780:4d:acac:a94c:5a97:dff:4189 answers · 443	yes
www over IPv6 www.tanopay.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:4b:1359:4a3e:1823:79fd:3884 answers · 443✓ 2a02:4780:4d:2b3a:b361:b506:7e82:7ba 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:4a:d5a7:60ea:85b1:74b:60d4 → 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)	147.79.79.176 147.79.72.29
AAAA (IPv6)	2a02:4780:4a:d5a7:60ea:85b1:74b:60d4 2a02:4780:4d:acac:a94c:5a97:dff:4189

www.tanopay.app Has IPv6

Alias of	www.tanopay.app.cdn.hstgr.net
A (IPv4)	84.32.84.54 2.57.91.217
AAAA (IPv6)	2a02:4780:4b:1359:4a3e:1823:79fd:3884 2a02:4780:4d:2b3a:b361:b506:7e82:7ba

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 01:26:55 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    147.79.79.176, 147.79.72.29
AAAA (IPv6): 2a02:4780:4a:d5a7:60ea:85b1:74b:60d4, 2a02:4780:4d:acac:a94c:5a97:dff:4189
www AAAA:    2a02:4780:4b:1359:4a3e:1823:79fd:3884, 2a02:4780:4d:2b3a:b361:b506:7e82:7ba

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:4a:d5a7:60ea:85b1:74b:60d4: answers (TCP 443)
    2a02:4780:4d:acac:a94c:5a97:dff:4189: answers (TCP 443)
- www over IPv6: www.tanopay.app has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:4b:1359:4a3e:1823:79fd:3884: answers (TCP 443)
    2a02:4780:4d:2b3a:b361:b506:7e82:7ba: 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:4a:d5a7:60ea:85b1:74b:60d4 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/ND94riSkug

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

Checked 2026-10-31 01:26:55 UTC. Full DNS report: dns.pizza/domain/tanopay.app · JSON: /api/v1/tanopay.app