Yes — gateqr.app has IPv6.

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

This is a saved measurement from 2026-11-06 11:40 UTC. Check gateqr.app live now

IPv6 readiness

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

Website over IPv6 gateqr.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:1cd answers · 443✓ 2606:4700:3035::ac43:81e9 answers · 443	yes
www over IPv6 www.gateqr.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3035::ac43:81e9 answers · 443✓ 2606:4700:3030::6815:1cd 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. isabel.ns.cloudflare.com ✓kayden.ns.cloudflare.com ✓	yes

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

https://gateqr.app/ via 2606:4700:3030::6815:1cd → 403

works

What's keeping gateqr.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

gateqr.app Has IPv6

A (IPv4)	104.21.1.205 172.67.129.233
AAAA (IPv6)	2606:4700:3030::6815:1cd 2606:4700:3035::ac43:81e9

www.gateqr.app Has IPv6

A (IPv4)	104.21.1.205 172.67.129.233
AAAA (IPv6)	2606:4700:3035::ac43:81e9 2606:4700:3030::6815:1cd

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: gateqr.app
Measured 2026-11-06 11:40:04 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.1.205, 172.67.129.233
AAAA (IPv6): 2606:4700:3030::6815:1cd, 2606:4700:3035::ac43:81e9
www AAAA:    2606:4700:3035::ac43:81e9, 2606:4700:3030::6815:1cd

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: gateqr.app has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:1cd: answers (TCP 443)
    2606:4700:3035::ac43:81e9: answers (TCP 443)
- www over IPv6: www.gateqr.app has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3035::ac43:81e9: answers (TCP 443)
    2606:4700:3030::6815:1cd: 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 403.
    https://gateqr.app/ via 2606:4700:3030::6815:1cd -> HTTP 403, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/OCBtLFhR7u

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

Checked 2026-11-06 11:40:04 UTC. Full DNS report: dns.pizza/domain/gateqr.app · Age, certificate and blocklists: how.is/gateqr.app · JSON: /api/v1/gateqr.app