Renewal History
xn--72czpba0b2an4cwaa9b8c2b3l4e.com
xn--72czpba0b2an4cwaa9b8c2b3l4e.com has been renewed 4 times, usually 4 years at a time. No near-death on record.
Every renewal, newest first
- 2023between Sep 26, 2020 and Dec 21, 2023+4 yearsexpiry Sep 14, 2020 → Sep 14, 2024After expiryup to 39 months after expiryTransferred: Name.com, Inc. → GoDaddy.com, LLC
- 2020between Sep 27, 2016 and Sep 26, 2020+3 yearsexpiry Sep 14, 2017 → Sep 14, 2020Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2016between Jun 22, 2013 and Sep 27, 2016+4 yearsexpiry Sep 14, 2013 → Sep 14, 2017Around expirysnapshots too far apart to say how early
- 2011between Nov 19, 2010 and Nov 15, 2011+2 yearsexpiry Sep 14, 2011 → Sep 14, 2013Around expirysnapshots too far apart to say how early
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: 9 snapshots of xn--72czpba0b2an4cwaa9b8c2b3l4e.com from the who.is WHOIS/RDAP archive, 2010-11-19 to 2024-06-20. Ledger built 2026-09-27.