Yes — xn--mi3bz0simh.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--mi3bz0simh.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:3cc2 answers · 443✓ 2606:4700:3036::ac43:c841 answers · 443	yes
www over IPv6 www.xn--mi3bz0simh.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:3cc2 answers · 443✓ 2606:4700:3036::ac43:c841 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. aisha.ns.cloudflare.com ✓merlin.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 403.

https://xn--mi3bz0simh.com/ via 2606:4700:3030::6815:3cc2 → 403

works

What's keeping xn--mi3bz0simh.com 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

xn--mi3bz0simh.com Has IPv6

A (IPv4)	104.21.60.194 172.67.200.65
AAAA (IPv6)	2606:4700:3030::6815:3cc2 2606:4700:3036::ac43:c841

www.xn--mi3bz0simh.com Has IPv6

A (IPv4)	104.21.60.194 172.67.200.65
AAAA (IPv6)	2606:4700:3030::6815:3cc2 2606:4700:3036::ac43:c841

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--mi3bz0simh.com
Measured 2026-11-09 17:05:11 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.60.194, 172.67.200.65
AAAA (IPv6): 2606:4700:3030::6815:3cc2, 2606:4700:3036::ac43:c841
www AAAA:    2606:4700:3030::6815:3cc2, 2606:4700:3036::ac43:c841

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn--mi3bz0simh.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:3cc2: answers (TCP 443)
    2606:4700:3036::ac43:c841: answers (TCP 443)
- www over IPv6: www.xn--mi3bz0simh.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:3cc2: answers (TCP 443)
    2606:4700:3036::ac43:c841: 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): Loads over IPv6 with a valid certificate: HTTP 403.
    https://xn--mi3bz0simh.com/ via 2606:4700:3030::6815:3cc2 -> HTTP 403, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/2s6gEEtCAV

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

Checked 2026-11-09 17:05:11 UTC. Full DNS report: dns.pizza/domain/xn--mi3bz0simh.com · Age, certificate and blocklists: how.is/xn--mi3bz0simh.com · JSON: /api/v1/xn--mi3bz0simh.com