Renewal History
xn--22c3bk1bj2c4h7bm.com
xn--22c3bk1bj2c4h7bm.com has been renewed 2 times, usually 3 years at a time. The longest single renewal was 4 years, around 2024, out to 2025. No near-death on record.
Every renewal, newest first
- 2024between Apr 26, 2020 and Aug 21, 2024+4 yearsexpiry Mar 29, 2021 → Mar 29, 2025Around expirysnapshots too far apart to say how early
- 2020between Mar 23, 2017 and Apr 26, 2020Re-registeredexpiry Sep 25, 2017 → Mar 29, 2021Dropped & re-registereda new registration, not a renewalTransferred: FastDomain Inc. → PDR Ltd. d/b/a PublicDomainRegistry.com
- 2017between Jan 6, 2014 and Mar 23, 2017+3 yearsexpiry Sep 25, 2014 → Sep 25, 2017Around expirysnapshots too far apart to say how early
- 2014between Oct 8, 2010 and Jan 6, 2014Re-registeredexpiry Dec 22, 2010 → Sep 25, 2014Dropped & re-registereda new registration, not a renewal
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: 5 snapshots of xn--22c3bk1bj2c4h7bm.com from the who.is WHOIS/RDAP archive, 2010-10-08 to 2024-08-21. Ledger built 2026-09-27.