Renewal History
kernlab.org
kernlab.org has been renewed 4 times, usually 1 year at a time. It came close to lapsing 2 times.
Every renewal, newest first
- 2025between Nov 26, 2024 and Sep 15, 2025+1 yearexpiry Jul 8, 2025 → Jul 8, 2026Around expirysnapshots too far apart to say how early
- 2024between Apr 6, 2024 and Aug 9, 2024+1 yearexpiry Jul 8, 2024 → Jul 8, 2025Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2023between Jul 2, 2023 and Aug 12, 2023Re-registeredexpiry Apr 21, 2023 → Jul 8, 2024Dropped & re-registereda new registration, not a renewalTransferred: IONOS SE → Sav.com, LLC - 41Redemption / pending delete seen
- 2023between Jan 16, 2022 and Jan 9, 2023+1 yearexpiry Apr 21, 2022 → Apr 21, 2023Around expirysnapshots too far apart to say how earlyTransferred: IONOS SE → 1&1 IONOS SERedemption / pending delete seen
- 2021between Feb 4, 2021 and Sep 23, 2021+1 yearexpiry Apr 21, 2021 → Apr 21, 2022Around expirysnapshots too far apart to say how early
- 2020between Jul 1, 2016 and Sep 19, 2020Re-registeredexpiry Mar 30, 2017 → Apr 21, 2021Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → 1&1 IONOS SE
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: 42 snapshots of kernlab.org from the who.is WHOIS/RDAP archive, 2016-07-01 to 2026-05-15. Ledger built 2026-09-27.