dns.pizza

Renewal History

googleaps.com

googleaps.com has been renewed 10 times, usually 1 year at a time, about 4 weeks before expiry. The longest single renewal was 5 years, around 2016, out to 2016. No near-death on record.

Renewals on record
10
Longest renewal
5 years
Expires
Sep 21, 2026
as of the latest snapshot
Snapshots
21
2011–2025

Every renewal, newest first

  1. 2025
    between Jan 12, 2025 and Oct 2, 2025
    +1 yearexpiry Sep 21, 2025 → Sep 21, 2026Around expiry
    snapshots too far apart to say how early
  2. 2025
    between Apr 2, 2024 and Jan 12, 2025
    +1 yearexpiry Sep 21, 2024 → Sep 21, 2025Around expiry
    snapshots too far apart to say how early
    Transferred: ConnectWave co.,Ltd → Megazone Corp., dba HOSTING.KR
  3. 2023
    between Jul 31, 2023 and Sep 12, 2023
    +1 yearexpiry Sep 21, 2023 → Sep 21, 2024Early
    1 to 7 weeks before expiry
  4. 2023
    between Aug 3, 2022 and Jul 31, 2023
    +1 yearexpiry Sep 21, 2022 → Sep 21, 2023Around expiry
    snapshots too far apart to say how early
  5. 2022
    between May 28, 2021 and Aug 3, 2022
    +1 yearexpiry Sep 21, 2021 → Sep 21, 2022Around expiry
    snapshots too far apart to say how early
    Transferred: Megazone Corp., dba HOSTING.KR → Koreacenter co.,Ltd
  6. 2021
    between Jul 7, 2020 and May 28, 2021
    +1 yearexpiry Sep 21, 2020 → Sep 21, 2021Around expiry
    snapshots too far apart to say how early
  7. 2019
    between Jun 26, 2018 and Dec 29, 2019
    +2 yearsexpiry Sep 21, 2018 → Sep 21, 2020Around expiry
    snapshots too far apart to say how early
  8. 2018
    between Jun 30, 2017 and Jun 26, 2018
    +1 yearexpiry Sep 21, 2017 → Sep 21, 2018Around expiry
    snapshots too far apart to say how early
  9. 2017
    between Sep 9, 2016 and Jan 14, 2017
    +1 yearexpiry Sep 21, 2016 → Sep 21, 2017Around expiry
    snapshots too far apart to say how early
  10. 2016
    between Aug 31, 2011 and Jul 25, 2016
    +5 yearsexpiry Sep 21, 2011 → Sep 21, 2016Around expiry
    snapshots too far apart to say how early
    Transferred: TODAY AND TOMORROW CO. LTD. → Megazone Corp., dba HOSTING.KR

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 googleaps.com from the who.is WHOIS/RDAP archive, 2011-03-06 to 2025-11-13. Ledger built 2026-09-27.

Back to googleaps.com report