Renewal History
testbook.com
testbook.com has been renewed 6 times, usually 2 years at a time, about 27 months before expiry. The longest single renewal was 8 years, around 2017, out to 2027. No near-death on record.
Every renewal, newest first
- 2024between Dec 7, 2023 and Jan 7, 2024+2 yearsexpiry Jan 8, 2027 → Jan 8, 2029Early36 to 37 months before expiry
- 2017between Jul 29, 2017 and Aug 2, 2017+8 yearsexpiry Jan 8, 2019 → Jan 8, 2027Early17 months before expiryRegistry confirmed an explicit renewal
- 2017between Dec 13, 2016 and Jan 15, 2017+2 yearsexpiry Jan 8, 2017 → Jan 8, 2019Around expirysnapshots too far apart to say how earlyTransferred: ENOM, INC. → Name.com, Inc.
- 2016between Aug 16, 2014 and Jul 2, 2016+2 yearsexpiry Jan 8, 2015 → Jan 8, 2017Around expirysnapshots too far apart to say how early
- 2013between May 15, 2013 and Dec 22, 2013+1 yearexpiry Jan 8, 2014 → Jan 8, 2015Early1 to 8 months before expiry
- 2013between Oct 28, 2012 and May 15, 2013+1 yearexpiry Jan 8, 2013 → Jan 8, 2014Around 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: 485 snapshots of testbook.com from the who.is WHOIS/RDAP archive, 2011-08-25 to 2026-05-20. Ledger built 2026-09-27.