dns.pizza

Renewal History

g9ogle.com

g9ogle.com has been renewed 14 times, usually 1 year at a time, about 3 weeks after expiry. The longest single renewal was 2 years, around 2016, out to 2017. It came close to lapsing 3 times.

Renewals on record
14
Longest renewal
2 years
Expires
Jul 31, 2026
as of the latest snapshot
Snapshots
351
2010–2026
Close calls
1
1 drop & re-registration

Every renewal, newest first

  1. 2025
    between Jul 12, 2025 and Aug 12, 2025
    +1 yearexpiry Jul 31, 2025 → Jul 31, 2026Around expiry
    snapshots too far apart to say how early
    Transferred: Gname 215 inc → Unstoppable Domains Inc.
  2. 2024
    between Jul 19, 2024 and Aug 30, 2024
    Re-registeredexpiry May 18, 2024 → Jul 31, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: 22net, Inc. → Gname 215 IncRedemption / pending delete seen
  3. 2023
    between Feb 18, 2023 and Aug 13, 2023
    +1 yearexpiry May 19, 2023 → May 19, 2024Around expiry
    snapshots too far apart to say how early
  4. 2022
    between May 29, 2022 and Jun 14, 2022
    +1 yearexpiry May 19, 2022 → May 19, 2023In grace period
    1 to 4 weeks after expiry
  5. 2021
    between May 22, 2021 and Jun 22, 2021
    +1 yearexpiry May 19, 2021 → May 19, 2022In grace period
    up to 5 weeks after expiry
  6. 2020
    between May 4, 2020 and Jun 6, 2020
    +1 yearexpiry May 19, 2020 → May 19, 2021Around expiry
    snapshots too far apart to say how early
  7. 2019
    between May 18, 2019 and Jun 18, 2019
    +1 yearexpiry May 19, 2019 → May 19, 2020Around expiry
    snapshots too far apart to say how early
  8. 2018
    between Apr 13, 2018 and Jun 15, 2018
    +1 yearexpiry May 19, 2018 → May 19, 2019Around expiry
    snapshots too far apart to say how early
  9. 2017
    between Jun 1, 2017 and Jun 4, 2017
    +1 yearexpiry May 19, 2017 → May 19, 2018In grace period
    2 weeks after expiry
  10. 2016
    between Nov 19, 2014 and Jun 21, 2016
    +2 yearsexpiry May 18, 2015 → May 19, 2017Around expiry
    snapshots too far apart to say how early
    Transferred: Mvpdomainnames.com LLC → 22NET, INC.
  11. 2014
    between May 18, 2014 and Jun 4, 2014
    +1 yearexpiry Mar 5, 2014 → May 18, 2015Late, past grace
    2 to 3 months after expiry
  12. 2014
    between Mar 6, 2014 and Mar 9, 2014
    +1 yearexpiry Mar 5, 2014 → Mar 5, 2015In grace period
    1 to 4 days after expiry
  13. 2013
    between Jan 31, 2013 and Mar 13, 2013
    +1 yearexpiry Mar 5, 2013 → Mar 5, 2014Around expiry
    snapshots too far apart to say how early
  14. 2012
    between May 3, 2012 and May 26, 2012
    +1 yearexpiry Mar 5, 2012 → Mar 5, 2013Late, past grace
    2 to 3 months after expiry
  15. 2012
    between Jan 31, 2011 and Mar 28, 2012
    +1 yearexpiry Dec 20, 2010 → Mar 5, 2012After expiry
    1 to 15 months after expiry

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: 351 snapshots of g9ogle.com from the who.is WHOIS/RDAP archive, 2010-06-15 to 2026-05-03. Ledger built 2026-09-27.

Back to g9ogle.com report