Renewal History
revolur.com
revolur.com has been renewed 2 times, usually 1 year at a time, about 5 months before expiry. No near-death on record.
Every renewal, newest first
- 2024between Feb 18, 2024 and Apr 13, 2024+1 yearexpiry Aug 2, 2024 → Aug 2, 2025Early4 to 5 months before expiry
- 2023between Jun 3, 2021 and Nov 30, 2023Re-registeredexpiry May 15, 2022 → Aug 2, 2024Dropped & re-registereda new registration, not a renewalTransferred: GMO INTERNET, INC. → COSMOTOWN, INC.
- 2021between Oct 5, 2020 and Jun 3, 2021+1 yearexpiry May 15, 2021 → May 15, 2022Around expirysnapshots too far apart to say how earlyTransferred: DNSPod, Inc. → GMO INTERNET, INC.
- 2020between Nov 23, 2018 and May 6, 2020Re-registeredexpiry Dec 3, 2018 → May 15, 2021Dropped & re-registereda new registration, not a renewalTransferred: Megazone Corp., dba HOSTING.KR → DNSPod, Inc.
- 2018between Feb 2, 2017 and Nov 23, 2018Re-registeredexpiry Feb 26, 2017 → Dec 3, 2018Dropped & re-registereda new registration, not a renewalTransferred: HICHINA ZHICHENG TECHNOLOGY LTD. → Megazone Corp., dba HOSTING.KR
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 revolur.com from the who.is WHOIS/RDAP archive, 2016-09-29 to 2024-04-13. Ledger built 2026-09-27.