Renewal History
ippfbe.org
ippfbe.org has been renewed 4 times, usually 2 years at a time. It came close to lapsing 3 times.
Every renewal, newest first
- 2025between Jul 8, 2025 and Aug 8, 2025Re-registeredexpiry May 1, 2025 → Jul 20, 2026Dropped & re-registereda new registration, not a renewalTransferred: Sav.com, LLC - 2 → Sav.com, LLC - 15Redemption / pending delete seen
- 2025between Apr 1, 2025 and May 16, 2025+1 yearexpiry May 1, 2025 → May 1, 2026Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2024between Apr 22, 2024 and May 30, 2024Re-registeredexpiry Feb 14, 2024 → May 1, 2025Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → Sav.com, LLC - 2Redemption / pending delete seen
- 2024between Jan 4, 2022 and Apr 22, 2024+2 yearsexpiry Feb 14, 2022 → Feb 14, 2024Around expirysnapshots too far apart to say how earlyRedemption / pending delete seen
- 2022between Sep 14, 2019 and Jan 4, 2022+2 yearsexpiry Feb 14, 2020 → Feb 14, 2022Around expirysnapshots too far apart to say how early
- 2018between Aug 13, 2016 and Nov 20, 2018+2 yearsexpiry Feb 14, 2018 → Feb 14, 2020Around expirysnapshots too far apart to say how early
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: 20 snapshots of ippfbe.org from the who.is WHOIS/RDAP archive, 2016-08-13 to 2026-05-14. Ledger built 2026-09-27.