Renewal History
blogers.org
blogers.org has been renewed 2 times, usually 1 year at a time, about 16 months before expiry. No near-death on record.
Every renewal, newest first
- 2026between Jan 21, 2026 and May 26, 2026Re-registeredexpiry Feb 9, 2026 → May 6, 2027Dropped & re-registereda new registration, not a renewalTransferred: NAMECHEAP INC → Key-Systems GmbH
- 2025between May 21, 2024 and Mar 19, 2025+1 yearexpiry Feb 9, 2025 → Feb 9, 2026Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2022between Sep 22, 2022 and Oct 24, 2022+1 yearexpiry Feb 9, 2024 → Feb 9, 2025Early16 to 17 months before expiryTransferred: PDR Ltd. d/b/a PublicDomainRegistry.com → NameCheap, Inc.
- 2022between Nov 9, 2017 and Mar 29, 2022Re-registeredexpiry Aug 8, 2018 → Feb 9, 2024Dropped & re-registereda new registration, not a renewalTransferred: Dynadot, LLC → PDR Ltd. d/b/a PublicDomainRegistry.com
- 2017between Feb 1, 2012 and Nov 9, 2017Re-registeredexpiry May 21, 2012 → Aug 8, 2018Dropped & re-registereda new registration, not a renewalTransferred: Key-Systems GmbH (R51-LROR) → Dynadot, LLC
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: 29 snapshots of blogers.org from the who.is WHOIS/RDAP archive, 2012-02-01 to 2026-05-26. Ledger built 2026-09-27.