Renewal History
mydb.info
mydb.info has been renewed once, usually 1 year at a time. It came close to lapsing 4 times.
Every renewal, newest first
- 2025between Jun 21, 2024 and Jul 28, 2025Re-registeredexpiry Mar 27, 2025 → Jul 27, 2026Dropped & re-registereda new registration, not a renewalTransferred: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn) → Porkbun LLC
- 2024between Mar 22, 2024 and Jun 21, 2024Re-registeredexpiry Jan 20, 2024 → Mar 27, 2025Dropped & re-registereda new registration, not a renewalTransferred: NameSilo, LLC → Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)Redemption / pending delete seen
- 2023between Dec 7, 2022 and Feb 3, 2023Re-registeredexpiry Oct 18, 2022 → Jan 20, 2024Dropped & re-registereda new registration, not a renewalTransferred: Dynadot, LLC → NameSilo, LLCRedemption / pending delete seen
- 2021between Sep 29, 2021 and Dec 30, 2021Re-registeredexpiry Aug 2, 2021 → Oct 18, 2022Dropped & re-registereda new registration, not a renewalTransferred: PDR Ltd. d/b/a PublicDomainRegistry.com → Dynadot, LLCRedemption / pending delete seen
- 2021between Aug 20, 2017 and Sep 29, 2021+1 yearexpiry Aug 2, 2020 → Aug 2, 2021Around expirysnapshots too far apart to say how earlyRedemption / pending delete seen
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: 19 snapshots of mydb.info from the who.is WHOIS/RDAP archive, 2017-08-20 to 2025-09-24. Ledger built 2026-09-27.