Yes — docadobe-shared.site has IPv6.

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

Measured 2026-11-05 09:43 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check docadobe-shared.site now

IPv6 readiness

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

Website over IPv6 docadobe-shared.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::ac43:c69f answers · 443✓ 2606:4700:3031::6815:157e answers · 443	yes
www over IPv6 www.docadobe-shared.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3031::6815:157e answers · 443✓ 2606:4700:3032::ac43:c69f 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. dalary.ns.cloudflare.com ✓david.ns.cloudflare.com ✓	yes

First measured 2026-11-05; last confirmed 2026-11-05.

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

https://docadobe-shared.site/ via 2606:4700:3032::ac43:c69f · timed out

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

docadobe-shared.site Has IPv6

A (IPv4)	104.21.21.126 172.67.198.159
AAAA (IPv6)	2606:4700:3032::ac43:c69f 2606:4700:3031::6815:157e

www.docadobe-shared.site Has IPv6

A (IPv4)	172.67.198.159 104.21.21.126
AAAA (IPv6)	2606:4700:3031::6815:157e 2606:4700:3032::ac43:c69f

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: docadobe-shared.site
Measured 2026-11-05 09:43:15 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.21.126, 172.67.198.159
AAAA (IPv6): 2606:4700:3032::ac43:c69f, 2606:4700:3031::6815:157e
www AAAA:    2606:4700:3031::6815:157e, 2606:4700:3032::ac43:c69f

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

Permanent link: aaaa.bot/r/B9wZ-Kr4cx · How we measure

Checked 2026-11-05 09:43:15 UTC. Full DNS report: dns.pizza/domain/docadobe-shared.site · Age, certificate and blocklists: how.is/docadobe-shared.site · JSON: /api/v1/docadobe-shared.site