xn--zckp1cyg736no7b03yf5lnuq.xyz
Lineage
May 9, 2014 → Oct 26, 2026Registry record since 2018 · 2 renewals on record · DNS at sedoparking.com · 2 nameserver changes seen.
What changed
- Missing from the zone file, then back between Apr 17, 2018 and Oct 24, 2026Listed on 2018-04-17, missing from the next held snapshot, listed again on 2026-10-24. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to sedoparking.com between Apr 17, 2018 and Oct 24, 2026ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp → ns1.sedoparking.com, ns2.sedoparking.com.
- Renewed +1 year between Apr 8, 2023 and Oct 4, 2024Expiry moved from 2024-09-13 to 2025-09-13, at GMO INTERNET, INC.
- Renewed +5 years between Jun 22, 2019 and Apr 8, 2023Expiry moved from 2019-09-13 to 2024-09-13, at GMO INTERNET, INC.
- DNS moved to xserver.jp between Mar 13, 2016 and Mar 14, 2016dns1.onamae.com, dns2.onamae.com → ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp.
Registrar and renewals: 4 WHOIS/RDAP snapshots, 2018-11-20 to 2024-10-04 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 168 .xyz zone-file snapshots held, 2014-05-09 to 2026-10-25.
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--zckp1cyg736no7b03yf5lnuq.xyz changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.