Yes — xn--ok0b82d2y8b.com 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 xn--ok0b82d2y8b.com 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
www over IPv6 www.xn--ok0b82d2y8b.com 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
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mail1.namebrightmail.com ✗mail2.namebrightmail.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns2.namebrightdns.com ✓ns1.namebrightdns.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
xn--ok0b82d2y8b.com didn't complete an HTTPS request over IPv6 (connection closed before a response).

https://xn--ok0b82d2y8b.com/ via 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd · connection closed before a response

What's keeping xn--ok0b82d2y8b.com from an A

Mail servers without IPv6
mail1.namebrightmail.com, mail2.namebrightmail.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

xn--ok0b82d2y8b.com Has IPv6

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

www.xn--ok0b82d2y8b.com Has IPv6

Alias of	comingsoon.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:c607:5974:bfa8:d54b:7fe5 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd

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: xn--ok0b82d2y8b.com
Measured 2026-10-31 10:05:24 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:c608:1ae1:9fc3:6ee2:84dd, 2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5
www AAAA:    2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5, 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn--ok0b82d2y8b.com 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)
- www over IPv6: www.xn--ok0b82d2y8b.com 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)
- 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): xn--ok0b82d2y8b.com didn't complete an HTTPS request over IPv6 (connection closed before a response).
    https://xn--ok0b82d2y8b.com/ via 2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd (connection closed before a response)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/Q9Qrc2Yo_w

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

Checked 2026-10-31 10:05:24 UTC. Full DNS report: dns.pizza/domain/xn--ok0b82d2y8b.com · JSON: /api/v1/xn--ok0b82d2y8b.com