xn--9t4b21ghxefvc.net
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for xn--9t4b21ghxefvc.net. Run the check on aaaa.bot →
Lineage
Our records: Oct 18, 2013 → Nov 1, 2026Oldest registry snapshot we hold: 2024 · 0 renewals on record · DNS at cypack.com · 2 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
What changed
- Missing from the zone file, then back between Aug 13, 2026 and Oct 29, 2026Listed on 2026-08-13, missing from the next held snapshot, listed again on 2026-10-29. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to nemoweb.co.kr between Apr 1, 2016 and Sep 3, 2016ns1.cafe24.co.kr, ns1.cafe24.com, ns2.cafe24.co.kr, ns2.cafe24.com → ns1.nemoweb.co.kr, ns2.nemoweb.co.kr.
- Missing from the zone file, then back between Nov 1, 2013 and May 1, 2014Listed on 2013-11-01, missing from the next held snapshot, listed again on 2014-05-01. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to cafe24.co.kr + cafe24.com between Nov 1, 2013 and May 1, 2014kns3.ktdom.com, kns4.ktdom.com → ns1.cafe24.co.kr, ns1.cafe24.com, ns2.cafe24.co.kr, ns2.cafe24.com.
Registrar and renewals: 2 WHOIS/RDAP snapshots, 2024-01-27 to 2024-04-25 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 105 .net zone-file snapshots held, 2013-10-18 to 2026-11-01.
Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.
Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.
Want to know when xn--9t4b21ghxefvc.net changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.