Yes — mworker.space 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 mworker.space has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3031::ac43:b050 answers · 443✓ 2606:4700:3034::6815:5866 answers · 443	yes
www over IPv6 www.mworker.space has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3034::6815:5866 answers · 443✓ 2606:4700:3031::ac43:b050 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. carioca.ns.cloudflare.com ✓otto.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Answered over IPv6 with a server error (HTTP 530) — can't tell whether that's specific to IPv6.

https://mworker.space/ via 2606:4700:3031::ac43:b050 → 530

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

mworker.space Has IPv6

A (IPv4)	172.67.176.80 104.21.88.102
AAAA (IPv6)	2606:4700:3031::ac43:b050 2606:4700:3034::6815:5866

www.mworker.space Has IPv6

A (IPv4)	104.21.88.102 172.67.176.80
AAAA (IPv6)	2606:4700:3034::6815:5866 2606:4700:3031::ac43:b050

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: mworker.space
Measured 2026-11-14 15:24:04 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    172.67.176.80, 104.21.88.102
AAAA (IPv6): 2606:4700:3031::ac43:b050, 2606:4700:3034::6815:5866
www AAAA:    2606:4700:3034::6815:5866, 2606:4700:3031::ac43:b050

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: mworker.space has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3031::ac43:b050: answers (TCP 443)
    2606:4700:3034::6815:5866: answers (TCP 443)
- www over IPv6: www.mworker.space has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3034::6815:5866: answers (TCP 443)
    2606:4700:3031::ac43:b050: 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): Answered over IPv6 with a server error (HTTP 530) — can't tell whether that's specific to IPv6.
    https://mworker.space/ via 2606:4700:3031::ac43:b050 -> HTTP 530, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/2zi_C3c9Mm

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

Checked 2026-11-14 15:24:04 UTC. Full DNS report: dns.pizza/domain/mworker.space · Age, certificate and blocklists: how.is/mworker.space · JSON: /api/v1/mworker.space