google30.com
Lineage
Oct 18, 2013 → Oct 29, 2026Registry record since 2018 · 1 renewal on record · DNS at share-dns.com + share-dns.net · 4 nameserver changes seen.
What changed
- Missing from the zone file, then back between Sep 19, 2026 and Oct 28, 2026Listed on 2026-09-19, missing from the next held snapshot, listed again on 2026-10-28. 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 19, 2026 and Oct 28, 2026ns35.domaincontrol.com, ns36.domaincontrol.com → a10.share-dns.com, b10.share-dns.net.
- Renewed +2 years between Apr 7, 2019 and Oct 2, 2020Expiry moved from 2019-08-08 to 2021-08-08, at GoDaddy.com, LLC.
- DNS moved to GoDaddy between Apr 1, 2016 and Apr 3, 2018ns1.bluehost.com, ns2.bluehost.com → ns35.domaincontrol.com, ns36.domaincontrol.com.
- Missing from the zone file, then back between Mar 27, 2015 and Nov 1, 2015Listed on 2015-03-27, missing from the next held snapshot, listed again on 2015-11-01. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to Bluehost between Mar 27, 2015 and Nov 1, 2015ns1.sharjfa.com, ns2.sharjfa.com → ns1.bluehost.com, ns2.bluehost.com.
- DNS moved to sharjfa.com between Jun 1, 2014 and Jan 24, 2015ns1.rozblog.com, ns2.rozblog.com → ns1.sharjfa.com, ns2.sharjfa.com.
Registrar and renewals: 4 WHOIS/RDAP snapshots, 2018-10-23 to 2021-04-11 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 102 .com zone-file snapshots held, 2013-10-18 to 2026-10-28.
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 google30.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.