Yes — datarecoveryseattle.net 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 datarecoveryseattle.net has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::ac43:ac0d answers · 443✓ 2606:4700:3035::6815:3fda answers · 443	yes
www over IPv6 www.datarecoveryseattle.net has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::ac43:ac0d answers · 443✓ 2606:4700:3035::6815:3fda 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. art.ns.cloudflare.com ✓pat.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 but ends on plain HTTP, not HTTPS after 1 redirect: HTTP 200.

https://datarecoveryseattle.net/ via 2606:4700:3030::ac43:ac0d → 301http://www.datarecoveryseattle.net/ via 2606:4700:3030::ac43:ac0d → 200

works

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

datarecoveryseattle.net Has IPv6

A (IPv4)	104.21.63.218 172.67.172.13
AAAA (IPv6)	2606:4700:3030::ac43:ac0d 2606:4700:3035::6815:3fda

www.datarecoveryseattle.net Has IPv6

A (IPv4)	104.21.63.218 172.67.172.13
AAAA (IPv6)	2606:4700:3030::ac43:ac0d 2606:4700:3035::6815:3fda

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: datarecoveryseattle.net
Measured 2026-11-15 14:21:46 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.63.218, 172.67.172.13
AAAA (IPv6): 2606:4700:3030::ac43:ac0d, 2606:4700:3035::6815:3fda
www AAAA:    2606:4700:3030::ac43:ac0d, 2606:4700:3035::6815:3fda

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: datarecoveryseattle.net has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::ac43:ac0d: answers (TCP 443)
    2606:4700:3035::6815:3fda: answers (TCP 443)
- www over IPv6: www.datarecoveryseattle.net has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::ac43:ac0d: answers (TCP 443)
    2606:4700:3035::6815:3fda: 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 but ends on plain HTTP, not HTTPS after 1 redirect: HTTP 200.
    https://datarecoveryseattle.net/ via 2606:4700:3030::ac43:ac0d -> HTTP 301, certificate: valid
    http://www.datarecoveryseattle.net/ via 2606:4700:3030::ac43:ac0d -> HTTP 200
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/6l8TSE-aEO

Permanent link: aaaa.bot/r/6l8TSE-aEO · How we measure

Checked 2026-11-15 14:21:46 UTC. Full DNS report: dns.pizza/domain/datarecoveryseattle.net · Age, certificate and blocklists: how.is/datarecoveryseattle.net · JSON: /api/v1/datarecoveryseattle.net