Renewal History
cloudfunctions.net
cloudfunctions.net has been renewed 9 times, usually 1 year at a time, about 5 weeks before expiry. No near-death on record.
Every renewal, newest first
- 2025between Oct 16, 2025 and Dec 14, 2025+1 yearexpiry Dec 3, 2025 → Dec 3, 2026Around expirysnapshots too far apart to say how early
- 2024between Oct 24, 2024 and Nov 1, 2024+1 yearexpiry Dec 3, 2024 → Dec 3, 2025Early5 to 6 weeks before expiry
- 2023between Oct 24, 2023 and Nov 6, 2023+1 yearexpiry Dec 3, 2023 → Dec 3, 2024Early4 to 6 weeks before expiry
- 2022between Oct 27, 2022 and Nov 1, 2022+1 yearexpiry Dec 3, 2022 → Dec 3, 2023Early5 weeks before expiry
- 2021between Oct 26, 2021 and Nov 8, 2021+1 yearexpiry Dec 3, 2021 → Dec 3, 2022Early4 to 5 weeks before expiry
- 2020between Oct 12, 2020 and Nov 1, 2020+1 yearexpiry Dec 3, 2020 → Dec 3, 2021Early5 to 7 weeks before expiry
- 2019between Oct 21, 2019 and Nov 13, 2019+1 yearexpiry Dec 3, 2019 → Dec 3, 2020Early3 to 6 weeks before expiry
- 2018between Oct 30, 2018 and Nov 16, 2018+1 yearexpiry Dec 3, 2018 → Dec 3, 2019Early2 to 5 weeks before expiry
- 2017between Oct 17, 2017 and Nov 17, 2017+1 yearexpiry Dec 3, 2017 → Dec 3, 2018Early2 to 7 weeks before 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: 379 snapshots of cloudfunctions.net from the who.is WHOIS/RDAP archive, 2017-05-30 to 2026-05-22. Ledger built 2026-09-27.