Renewal History
xn--72czpba5eubsa1bzfzgoe.net
xn--72czpba5eubsa1bzfzgoe.net has been renewed 3 times, usually 1 year at a time. The longest single renewal was 3 years, around 2012, out to 2013. No near-death on record.
Every renewal, newest first
- 2024between Feb 18, 2024 and Aug 24, 2024+1 yearexpiry Sep 12, 2024 → Sep 12, 2025Early1 to 7 months before expiry
- 2024between Aug 25, 2021 and Feb 18, 2024Re-registeredexpiry Jun 23, 2022 → Sep 12, 2024Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → Name.com, Inc.
- 2021between Apr 1, 2020 and Aug 25, 2021Re-registeredexpiry Apr 1, 2021 → Jun 23, 2022Dropped & re-registereda new registration, not a renewalTransferred: Name.com, Inc. → GoDaddy.com, LLC
- 2020between May 13, 2013 and Apr 1, 2020Re-registeredexpiry Apr 8, 2014 → Apr 1, 2021Dropped & re-registereda new registration, not a renewal
- 2013between Dec 24, 2012 and Apr 27, 2013+1 yearexpiry Apr 8, 2013 → Apr 8, 2014Around expirysnapshots too far apart to say how early
- 2012between Aug 5, 2009 and Nov 24, 2012+3 yearsexpiry Apr 8, 2010 → Apr 8, 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: 13 snapshots of xn--72czpba5eubsa1bzfzgoe.net from the who.is WHOIS/RDAP archive, 2009-07-06 to 2024-08-24. Ledger built 2026-09-27.