dns.pizza

Renewal History

google0.com

google0.com has been renewed 5 times, usually 1 year at a time. The longest single renewal was 2 years, around 2016, out to 2016. No near-death on record.

Renewals on record
5
Longest renewal
2 years
Expires
May 23, 2025
as of the latest snapshot
Snapshots
21
2009–2024
Close calls
0
3 drops & re-registration

Every renewal, newest first

  1. 2024
    between Mar 25, 2024 and Jun 6, 2024
    Re-registeredexpiry Mar 6, 2024 → May 23, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: DropCatch.com 696 LLC → REALTIME REGISTER B.V.
  2. 2023
    between Aug 9, 2021 and Apr 18, 2023
    Re-registeredexpiry Dec 29, 2021 → Mar 6, 2024Dropped & re-registered
    a new registration, not a renewal
    Transferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → DropCatch.com 696 LLC
  3. 2021
    between Oct 30, 2020 and Aug 9, 2021
    +1 yearexpiry Dec 29, 2020 → Dec 29, 2021Around expiry
    snapshots too far apart to say how early
    Transferred: DNSPod, Inc. → Alibaba Cloud Computing (Beijing) Co., Ltd.
  4. 2020
    between Oct 1, 2018 and Jan 20, 2020
    +2 yearsexpiry Dec 29, 2018 → Dec 29, 2020Around expiry
    snapshots too far apart to say how early
    Transferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → DNSPod, Inc.
  5. 2018
    between Aug 5, 2017 and Jul 15, 2018
    +1 yearexpiry Dec 29, 2017 → Dec 29, 2018Around expiry
    snapshots too far apart to say how early
  6. 2017
    between Aug 2, 2016 and May 15, 2017
    +1 yearexpiry Dec 29, 2016 → Dec 29, 2017Around expiry
    snapshots too far apart to say how early
    Transferred: DYNADOT LLC → HICHINA ZHICHENG TECHNOLOGY LTD.
  7. 2016
    between Mar 14, 2014 and Aug 2, 2016
    +2 yearsexpiry Dec 29, 2014 → Dec 29, 2016Around expiry
    snapshots too far apart to say how early
    Transferred: Bravenames Inc → DYNADOT LLC
  8. 2014
    between Oct 2, 2009 and Mar 14, 2014
    Re-registeredexpiry Oct 19, 2010 → Dec 29, 2014Dropped & 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: 21 snapshots of google0.com from the who.is WHOIS/RDAP archive, 2009-10-02 to 2024-07-09. Ledger built 2026-09-27.

Back to google0.com report