Renewal History
contextweb.com
contextweb.com has been renewed 4 times, usually 3 years at a time, about 8 weeks before expiry. No near-death on record.
Every renewal, newest first
- 2026between Jan 4, 2026 and Feb 8, 2026+3 yearsexpiry Mar 16, 2026 → Mar 16, 2029Early1 to 2 months before expiry
- 2023between Dec 13, 2022 and Feb 5, 2023+3 yearsexpiry Mar 16, 2023 → Mar 16, 2026Early1 to 3 months before expiry
- 2020between Jan 9, 2020 and Jan 25, 2020+3 yearsexpiry Mar 16, 2020 → Mar 16, 2023Early2 months before expiry
- 2017between Dec 20, 2016 and Jan 21, 2017Re-registeredexpiry Mar 16, 2017 → Mar 16, 2020Dropped & re-registereda new registration, not a renewal
- 2014between Jan 13, 2014 and Feb 15, 2014+3 yearsexpiry Mar 16, 2014 → Mar 16, 2017Early1 to 2 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: 156 snapshots of contextweb.com from the who.is WHOIS/RDAP archive, 2011-09-11 to 2026-05-31. Ledger built 2026-09-27.