Yes — flareadobe-shared.site has IPv6.

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

This is a saved measurement from 2026-11-02 07:46 UTC. Check flareadobe-shared.site live now

IPv6 readiness

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

Website over IPv6 flareadobe-shared.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:1f0a answers · 443✓ 2606:4700:3030::ac43:ae9d answers · 443	yes
www over IPv6 www.flareadobe-shared.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:1f0a answers · 443✓ 2606:4700:3030::ac43:ae9d 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. autumn.ns.cloudflare.com ✓dale.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
flareadobe-shared.site didn't complete an HTTPS request over IPv6 (timed out).

https://flareadobe-shared.site/ via 2606:4700:3030::6815:1f0a · timed out

What's keeping flareadobe-shared.site 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

flareadobe-shared.site Has IPv6

A (IPv4)	104.21.31.10 172.67.174.157
AAAA (IPv6)	2606:4700:3030::6815:1f0a 2606:4700:3030::ac43:ae9d

www.flareadobe-shared.site Has IPv6

A (IPv4)	172.67.174.157 104.21.31.10
AAAA (IPv6)	2606:4700:3030::6815:1f0a 2606:4700:3030::ac43:ae9d

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: flareadobe-shared.site
Measured 2026-11-02 07:46:19 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.31.10, 172.67.174.157
AAAA (IPv6): 2606:4700:3030::6815:1f0a, 2606:4700:3030::ac43:ae9d
www AAAA:    2606:4700:3030::6815:1f0a, 2606:4700:3030::ac43:ae9d

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: flareadobe-shared.site has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:1f0a: answers (TCP 443)
    2606:4700:3030::ac43:ae9d: answers (TCP 443)
- www over IPv6: www.flareadobe-shared.site has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:1f0a: answers (TCP 443)
    2606:4700:3030::ac43:ae9d: 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): flareadobe-shared.site didn't complete an HTTPS request over IPv6 (timed out).
    https://flareadobe-shared.site/ via 2606:4700:3030::6815:1f0a, certificate: valid (timed out)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/zqYChkF8Wg

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

Checked 2026-11-02 07:46:19 UTC. Full DNS report: dns.pizza/domain/flareadobe-shared.site · JSON: /api/v1/flareadobe-shared.site