Renewal History
isolo.mobi
isolo.mobi has been renewed 2 times, usually 1 year at a time, about 8 days after expiry. It came close to lapsing 4 times.
Every renewal, newest first
- 2025between Jul 5, 2025 and Jul 11, 2025+1 yearexpiry Jun 30, 2025 → Jun 30, 2026In grace period5 to 11 days after expiryRegistry auto-renew
- 2024between Oct 1, 2023 and Oct 10, 2024Re-registeredexpiry Aug 2, 2023 → Jun 30, 2025Dropped & re-registereda new registration, not a renewalTransferred: NameCheap, Inc. → Porkbun LLCRedemption / pending delete seen
- 2022between Oct 26, 2021 and Oct 7, 2022Re-registeredexpiry Aug 26, 2021 → Aug 2, 2023Dropped & re-registereda new registration, not a renewalRedemption / pending delete seenRegistry showed it unregistered
- 2020between Jul 10, 2020 and Sep 22, 2020+1 yearexpiry Aug 26, 2020 → Aug 26, 2021Around expirysnapshots too far apart to say how earlyRegistry auto-renewRedemption / pending delete seen
- 2019between Jul 13, 2018 and Sep 25, 2019Re-registeredexpiry Jul 21, 2018 → Aug 26, 2020Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → NAMECHEAP INCRegistry showed it unregistered
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: 38 snapshots of isolo.mobi from the who.is WHOIS/RDAP archive, 2018-05-02 to 2026-02-10. Ledger built 2026-09-27.