Renewal History
resume.com
resume.com has been renewed 7 times, usually 1 year at a time, about 5 weeks before expiry. The longest single renewal was 2 years, around 2016, out to 2020. No near-death on record.
Every renewal, newest first
- 2025between Oct 21, 2025 and Nov 10, 2025+1 yearexpiry Dec 2, 2025 → Dec 2, 2026Early3 to 6 weeks before expiry
- 2024between Oct 24, 2024 and Nov 21, 2024+1 yearexpiry Dec 2, 2024 → Dec 2, 2025Early2 to 6 weeks before expiry
- 2023between Sep 3, 2023 and Oct 31, 2023+1 yearexpiry Dec 2, 2023 → Dec 2, 2024Early1 to 3 months before expiry
- 2022between Oct 11, 2022 and Nov 12, 2022+1 yearexpiry Dec 2, 2022 → Dec 2, 2023Early3 to 7 weeks before expiry
- 2021between Oct 19, 2021 and Nov 3, 2021+1 yearexpiry Dec 2, 2021 → Dec 2, 2022Early4 to 6 weeks before expiry
- 2018between May 6, 2018 and Jun 16, 2018+1 yearexpiry Dec 2, 2020 → Dec 2, 2021Early30 to 31 months before expiryTransferred: TUCOWS, INC. → MarkMonitor, Inc.
- 2016between Jun 19, 2014 and Jul 25, 2016+2 yearsexpiry Dec 2, 2018 → Dec 2, 2020Early28 to 53 months before expiryTransferred: ENOM, INC. → TUCOWS, INC.
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: 446 snapshots of resume.com from the who.is WHOIS/RDAP archive, 2009-04-19 to 2026-05-26. Ledger built 2026-09-27.