Yes — wordpressconnect.net has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 wordpressconnect.net has 2 IPv6 addresses and answers on every one we tested. ✓ 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5 answers · 443✓ 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd answers · 443	yes
www over IPv6 www.wordpressconnect.net has 2 IPv6 addresses and answers on every one we tested. ✓ 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd answers · 443✓ 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5 answers · 443	yes
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns1.namebrightdns.com ✓ns2.namebrightdns.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.

https://wordpressconnect.net/ via 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5 → 301https://www.dropcatch.com/domain/wordpressconnect.net via 2606:4700:10::ac42:979a → 200

works

Nothing keeping you from an A

Nothing to fix
Show it off: add the badge to your README.
[![IPv6](https://aaaa.bot/badge/wordpressconnect.net.svg)](https://aaaa.bot/wordpressconnect.net)

Check again

wordpressconnect.net Has IPv6

A (IPv4)	54.84.240.235 44.208.83.180
AAAA (IPv6)	2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd

www.wordpressconnect.net Has IPv6

Alias of	urlforward-https.namebright.com → cdl-prd-https-247c6c9f427caacd.elb.us-east-1.amazonaws.com
A (IPv4)	44.208.83.180 54.84.240.235
AAAA (IPv6)	2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5

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: wordpressconnect.net
Measured 2026-11-06 06:07:41 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    54.84.240.235, 44.208.83.180
AAAA (IPv6): 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5, 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd
www AAAA:    2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd, 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: wordpressconnect.net has 2 IPv6 addresses and answers on every one we tested.
    2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5: answers (TCP 443)
    2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd: answers (TCP 443)
- www over IPv6: www.wordpressconnect.net has 2 IPv6 addresses and answers on every one we tested.
    2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd: answers (TCP 443)
    2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5: answers (TCP 443)
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It 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 with a valid certificate after 1 redirect: HTTP 200.
    https://wordpressconnect.net/ via 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5 -> HTTP 301, certificate: valid
    https://www.dropcatch.com/domain/wordpressconnect.net via 2606:4700:10::ac42:979a -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/3DkXy0B1U4

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

Checked 2026-11-06 06:07:41 UTC. Full DNS report: dns.pizza/domain/wordpressconnect.net · Age, certificate and blocklists: how.is/wordpressconnect.net · JSON: /api/v1/wordpressconnect.net