Yes — wordpress-messaging.fit has IPv6.

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

This is a saved measurement from 2026-11-01 17:34 UTC. Check wordpress-messaging.fit live now

IPv6 readiness

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

Website over IPv6 wordpress-messaging.fit has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3033::6815:3a28 answers · 443✓ 2606:4700:3036::ac43:9bf7 answers · 443	yes
www over IPv6 www.wordpress-messaging.fit has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3036::ac43:9bf7 answers · 443✓ 2606:4700:3033::6815:3a28 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. cameron.ns.cloudflare.com ✓nataly.ns.cloudflare.com ✓	yes

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

https://wordpress-messaging.fit/ via 2606:4700:3033::6815:3a28 → 520

What's keeping wordpress-messaging.fit 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

wordpress-messaging.fit Has IPv6

A (IPv4)	104.21.58.40 172.67.155.247
AAAA (IPv6)	2606:4700:3033::6815:3a28 2606:4700:3036::ac43:9bf7

www.wordpress-messaging.fit Has IPv6

A (IPv4)	104.21.58.40 172.67.155.247
AAAA (IPv6)	2606:4700:3036::ac43:9bf7 2606:4700:3033::6815:3a28

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: wordpress-messaging.fit
Measured 2026-11-01 17:34:45 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.58.40, 172.67.155.247
AAAA (IPv6): 2606:4700:3033::6815:3a28, 2606:4700:3036::ac43:9bf7
www AAAA:    2606:4700:3036::ac43:9bf7, 2606:4700:3033::6815:3a28

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: wordpress-messaging.fit has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3033::6815:3a28: answers (TCP 443)
    2606:4700:3036::ac43:9bf7: answers (TCP 443)
- www over IPv6: www.wordpress-messaging.fit has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3036::ac43:9bf7: answers (TCP 443)
    2606:4700:3033::6815:3a28: 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 520) — can't tell whether that's specific to IPv6.
    https://wordpress-messaging.fit/ via 2606:4700:3033::6815:3a28 -> HTTP 520, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/xUI52g_4NS

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

Checked 2026-11-01 17:34:45 UTC. Full DNS report: dns.pizza/domain/wordpress-messaging.fit · JSON: /api/v1/wordpress-messaging.fit