Renewal History
db-recovery.com
db-recovery.com has been renewed 3 times, usually 1 year at a time. The longest single renewal was 2 years, around 2024, out to 2025. No near-death on record.
Every renewal, newest first
- 2026between Jan 12, 2025 and Apr 13, 2026+1 yearexpiry Jun 14, 2025 → Jun 14, 2026Around expirysnapshots too far apart to say how early
- 2024between Apr 1, 2023 and Sep 11, 2024+2 yearsexpiry Jun 14, 2023 → Jun 14, 2025Around expirysnapshots too far apart to say how early
- 2023between Feb 16, 2022 and Apr 1, 2023+1 yearexpiry Jun 14, 2022 → Jun 14, 2023Around expirysnapshots too far apart to say how earlyTransferred: DropCatch.com 1243 LLC → Gname.com Pte. Ltd.
- 2021between Dec 1, 2019 and Jun 15, 2021Re-registeredexpiry Jan 11, 2020 → Jun 14, 2022Dropped & re-registereda new registration, not a renewal
- 2019between Jul 10, 2018 and Aug 9, 2019Re-registeredexpiry Oct 23, 2018 → Jan 11, 2020Dropped & re-registereda new registration, not a renewalTransferred: Heavydomains.net LLC → DropCatch.com 811 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: 11 snapshots of db-recovery.com from the who.is WHOIS/RDAP archive, 2018-07-10 to 2026-04-13. Ledger built 2026-09-27.