xxservice.top
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for xxservice.top. Run the check on aaaa.bot →
Lineage
Our records: Dec 18, 2015 → Nov 1, 2026Oldest registry snapshot we hold: 2025 · 0 renewals on record · DNS at julydns.com · 3 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
What changed
- DNS moved to julydns.com between Oct 20, 2026 and Oct 21, 2026a.share-dns.com, b.share-dns.net → ns1.julydns.com, ns2.julydns.com.
- Missing from the zone file, then back between Sep 14, 2026 and Oct 20, 2026Listed on 2026-09-14, missing from the next held snapshot, listed again on 2026-10-20. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to share-dns.com + share-dns.net between Sep 14, 2026 and Oct 20, 2026expirens3.hichina.com, expirens4.hichina.com → a.share-dns.com, b.share-dns.net.
- New nameservers at hichina.com between Aug 8, 2026 and Aug 9, 2026dns7.hichina.com, dns8.hichina.com → expirens3.hichina.com, expirens4.hichina.com.
Registrar and renewals: 5 WHOIS/RDAP snapshots, 2025-08-08 to 2026-05-15 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 153 .top zone-file snapshots held, 2015-12-18 to 2026-10-31.
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 xxservice.top changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.