Renewal History
blog.com
blog.com has been renewed 5 times, usually 3 years at a time, about 52 months before expiry. The longest single renewal was 9 years, around 2007, out to 2017. No near-death on record.
Every renewal, newest first
- 2023between Aug 19, 2023 and Sep 12, 2023+3 yearsexpiry Apr 13, 2030 → Apr 13, 2033Early79 to 80 months before expiry
- 2020between Nov 28, 2020 and Dec 4, 2020+5 yearsexpiry Apr 13, 2025 → Apr 13, 2030Early52 months before expiryTransferred: Key-Systems GmbH → REALTIME REGISTER B.V.
- 2016between Oct 12, 2014 and Jul 10, 2016+5 yearsexpiry Apr 13, 2020 → Apr 13, 2025Early45 to 66 months before expiryTransferred: Arsys Internet, S.L. dba NICLINE.COM → Key-Systems GmbH
- 2011between Apr 14, 2009 and Jun 30, 2011+3 yearsexpiry Apr 13, 2017 → Apr 13, 2020Early69 to 96 months before expiry
- 2007between Sep 29, 2007 and Oct 1, 2007+9 yearsexpiry Apr 13, 2008 → Apr 13, 2017Early6 months 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: 1,162 snapshots of blog.com from the who.is WHOIS/RDAP archive, 2007-05-11 to 2026-05-26. Ledger built 2026-09-27.