tracking-line.com
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for tracking-line.com. Run the check on aaaa.bot →
Lineage
Our records: Oct 18, 2013 → Nov 2, 2026DNS at my-ndns.com · 3 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 Apr 1, 2016 and Oct 16, 2026Listed on 2016-04-01, missing from the next held snapshot, listed again on 2026-10-16. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to my-ndns.com between Apr 1, 2016 and Oct 16, 2026ns1.servershost.net, ns2.servershost.net → ns3.my-ndns.com, ns4.my-ndns.com.
- DNS moved to servershost.net between Mar 1, 2016 and Apr 1, 2016ns1.atonproxy.net.2016-02-09.nsdns.info, ns2.atonproxy.net.2016-02-09.nsdns.info → ns1.servershost.net, ns2.servershost.net.
- DNS moved to nsdns.info between Feb 5, 2016 and Mar 1, 2016ns1.atonproxy.net, ns2.atonproxy.net → ns1.atonproxy.net.2016-02-09.nsdns.info, ns2.atonproxy.net.2016-02-09.nsdns.info.
Nameservers, registry zone files: 106 .com 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 tracking-line.com changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.