No — xn--o39a65k7mookcosdd41abuc51e.life is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

This is a saved measurement from 2026-10-31 04:37 UTC. Check xn--o39a65k7mookcosdd41abuc51e.life live now

IPv6 readiness

The website has no IPv6.

Website over IPv6 xn--o39a65k7mookcosdd41abuc51e.life has no AAAA record.	no
www over IPv6 www.xn--o39a65k7mookcosdd41abuc51e.life has no AAAA record.	no
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record.	no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns4.hosting.co.kr ✗ns2.hosting.co.kr ✗ns3.hosting.co.kr ✗ns1.hosting.co.kr ✗	no

What's keeping xn--o39a65k7mookcosdd41abuc51e.life from an A

Give xn--o39a65k7mookcosdd41abuc51e.life an IPv6 address
Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
www.xn--o39a65k7mookcosdd41abuc51e.life is hosted on Render, which has no IPv6
It points at handover-v8jg.onrender.com, and that name has no AAAA record — so nothing you add in your own DNS can give it IPv6. Put an IPv6-capable proxy in front (Cloudflare's proxied DNS does this), or host somewhere that offers IPv6. Which platforms offer IPv6
Mail servers without IPv6
Your domain's mail goes to its own address, which has no AAAA record.
Nameservers without IPv6
ns4.hosting.co.kr, ns2.hosting.co.kr, ns3.hosting.co.kr, ns1.hosting.co.kr all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

xn--o39a65k7mookcosdd41abuc51e.life IPv4 only

A (IPv4)	216.24.57.1
AAAA (IPv6)	none

www.xn--o39a65k7mookcosdd41abuc51e.life IPv4 only

Alias of	handover-v8jg.onrender.com → gcp-us-west1-1.origin.onrender.com → gcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net
A (IPv4)	216.24.57.16 216.24.57.18
AAAA (IPv6)	none

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: xn--o39a65k7mookcosdd41abuc51e.life
Measured 2026-10-31 04:37:05 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    216.24.57.1
AAAA (IPv6): none
www AAAA:    none

Readiness grade D: The website has no IPv6.
- Website over IPv6: xn--o39a65k7mookcosdd41abuc51e.life has no AAAA record.
- www over IPv6: www.xn--o39a65k7mookcosdd41abuc51e.life has no AAAA record.
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/EMmsfp2F3x

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

Checked 2026-10-31 04:37:05 UTC. Full DNS report: dns.pizza/domain/xn--o39a65k7mookcosdd41abuc51e.life · JSON: /api/v1/xn--o39a65k7mookcosdd41abuc51e.life