dns.pizza

Renewal History

go-google.com

go-google.com has been renewed once, usually 1 year at a time. It came close to lapsing 2 times.

Renewals on record
1
Longest renewal
1 year
Expires
May 8, 2026
as of the latest snapshot
Snapshots
13
2009–2026
Close calls
2
3 drops & re-registration

Every renewal, newest first

  1. 2025
    between Jan 14, 2020 and Jun 25, 2025
    Re-registeredexpiry Jul 25, 2020 → May 8, 2026Dropped & re-registered
    a new registration, not a renewal
    Transferred: DropCatch.com 1030 LLC → Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
  2. 2019
    between Jun 23, 2019 and Aug 31, 2019
    Re-registeredexpiry May 9, 2019 → Jul 25, 2020Dropped & re-registered
    a new registration, not a renewal
    Transferred: Net-Chinese Co., Ltd. → DropCatch.com 1030 LLCRedemption / pending delete seen
  3. 2018
    between Aug 12, 2017 and Aug 4, 2018
    +1 yearexpiry May 9, 2018 → May 9, 2019Around expiry
    snapshots too far apart to say how early
    Redemption / pending delete seen
  4. 2017
    between Mar 20, 2009 and Aug 12, 2017
    Re-registeredexpiry Apr 11, 2009 → May 9, 2018Dropped & re-registered
    a new registration, not a renewal

How this is worked out. Each renewal is a forward jump in the registry’s expiry date between two WHOIS or RDAP snapshots. The size of the jump is the number of years paid for. The renewal happened somewhere between the two snapshot dates, so how early or late it was is a range; when the snapshots are far apart, it is not stated.

For .com and .net the registry itself extends the expiry on the day it lapses and gives the registrar 45 days to pay or delete, so a jump right at expiry is not proof the owner paid. The ledger marks renewals the registry flagged as explicit, and near-deaths where it later showed a redemption or pending-delete status.

Source: 13 snapshots of go-google.com from the who.is WHOIS/RDAP archive, 2009-01-08 to 2026-04-16. Ledger built 2026-09-27.

Back to go-google.com report