Yes — xn--ok0b476a9udba558o.com has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 xn--ok0b476a9udba558o.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:41a6:b29d:f324:7143:2e45 answers · 443✓ 2a02:4780:84:959d:dec1:feb2:3623:a17f answers · 443	yes
www over IPv6 www.xn--ok0b476a9udba558o.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:f9b8:f9:1e2c:dfd:31f3 answers · 443✓ 2a02:4780:84:7ccf:549c:7e88:d8d3:1305 answers · 443	yes
Mail servers (MX) have IPv6 Every mail server has an AAAA record. mx1.hostinger.com ✓mx2.hostinger.com ✓	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. orbit.dns-parking.com ✓horizon.dns-parking.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Redirects to xn--om2bq8fl6duzy.com, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.

https://xn--ok0b476a9udba558o.com/ via 2a02:4780:84:41a6:b29d:f324:7143:2e45 → 301https://xn--om2bq8fl6duzy.com/ · redirects to xn--om2bq8fl6duzy.com, which has no IPv6 address

problem

Nothing keeping you from an A

A redirect leads off IPv6
Redirects to xn--om2bq8fl6duzy.com, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all. Give the redirect target IPv6 too, or redirect somewhere that has it.

Check again

xn--ok0b476a9udba558o.com Has IPv6

A (IPv4)	88.222.222.106 2.57.91.187
AAAA (IPv6)	2a02:4780:84:41a6:b29d:f324:7143:2e45 2a02:4780:84:959d:dec1:feb2:3623:a17f

www.xn--ok0b476a9udba558o.com Has IPv6

Alias of	www.xn--ok0b476a9udba558o.com.cdn.hstgr.net
A (IPv4)	145.223.124.145 147.79.79.229
AAAA (IPv6)	2a02:4780:84:f9b8:f9:1e2c:dfd:31f3 2a02:4780:84:7ccf:549c:7e88:d8d3:1305

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--ok0b476a9udba558o.com
Measured 2026-10-31 04:21:10 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    88.222.222.106, 2.57.91.187
AAAA (IPv6): 2a02:4780:84:41a6:b29d:f324:7143:2e45, 2a02:4780:84:959d:dec1:feb2:3623:a17f
www AAAA:    2a02:4780:84:f9b8:f9:1e2c:dfd:31f3, 2a02:4780:84:7ccf:549c:7e88:d8d3:1305

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: xn--ok0b476a9udba558o.com has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:41a6:b29d:f324:7143:2e45: answers (TCP 443)
    2a02:4780:84:959d:dec1:feb2:3623:a17f: answers (TCP 443)
- www over IPv6: www.xn--ok0b476a9udba558o.com has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:f9b8:f9:1e2c:dfd:31f3: answers (TCP 443)
    2a02:4780:84:7ccf:549c:7e88:d8d3:1305: answers (TCP 443)
- Mail servers (MX) have IPv6: Every mail server 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): Redirects to xn--om2bq8fl6duzy.com, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.
    https://xn--ok0b476a9udba558o.com/ via 2a02:4780:84:41a6:b29d:f324:7143:2e45 -> HTTP 301, certificate: valid
    https://xn--om2bq8fl6duzy.com/ (redirects to xn--om2bq8fl6duzy.com, which has no IPv6 address)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/71ReNlVeCh

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

Checked 2026-10-31 04:21:10 UTC. Full DNS report: dns.pizza/domain/xn--ok0b476a9udba558o.com · JSON: /api/v1/xn--ok0b476a9udba558o.com