vacationtimesharepoints.com
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for vacationtimesharepoints.com. Run the check on aaaa.bot →
Lineage
Our records: Oct 18, 2013 → Nov 1, 2026Oldest registry snapshot we hold: 2016 · 1 renewal on record · DNS at dns.com · 3 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
What changed
- DNS moved to dns.com between Oct 20, 2026 and Oct 21, 2026ns1.gname-dns.com, ns2.gname-dns.com → ns1.dns.com, ns2.dns.com.
- Missing from the zone file, then back between Sep 12, 2026 and Oct 20, 2026Listed on 2026-09-12, 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 gname-dns.com between Sep 12, 2026 and Oct 20, 2026ns1.pendingrenewaldeletion.com, ns2.pendingrenewaldeletion.com → ns1.gname-dns.com, ns2.gname-dns.com.
- DNS moved to pendingrenewaldeletion.com between Apr 3, 2018 and Aug 5, 2026ns1.infoquesthosting.net, ns2.infoquesthosting.net → ns1.pendingrenewaldeletion.com, ns2.pendingrenewaldeletion.com.
- Renewed +7 years between Dec 21, 2018 and Jan 18, 2026Expiry moved from 2019-07-31 to 2026-07-31, at Network Solutions, LLC.
Registrar and renewals: 4 WHOIS/RDAP snapshots, 2016-07-20 to 2026-01-18 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 105 .com zone-file snapshots held, 2013-10-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 vacationtimesharepoints.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.