Renewal History
xn--l3ca4btt2k1b.com
xn--l3ca4btt2k1b.com has been renewed 4 times, usually 1 year at a time. The longest single renewal was 3 years, around 2017, out to 2017. It came close to lapsing once.
Every renewal, newest first
- 2024between Feb 13, 2021 and Apr 20, 2024Re-registeredexpiry Mar 10, 2022 → Jun 5, 2024Dropped & re-registereda new registration, not a renewalTransferred: NAMECHEAP INC → GoDaddy.com, LLC
- 2021between Jun 5, 2020 and Feb 13, 2021+1 yearexpiry Mar 10, 2021 → Mar 10, 2022Early1 to 9 months before expiryRegistry confirmed an explicit renewal
- 2020between Mar 12, 2019 and May 22, 2020+1 yearexpiry Mar 10, 2020 → Mar 10, 2021Around expirysnapshots too far apart to say how early
- 2019between May 12, 2017 and Mar 12, 2019Re-registeredexpiry Dec 5, 2017 → Mar 10, 2020Dropped & re-registereda new registration, not a renewalTransferred: Name.com, Inc. → NAMECHEAP INCRegistry showed it unregistered
- 2017between Apr 24, 2014 and May 12, 2017+3 yearsexpiry Dec 5, 2014 → Dec 5, 2017Around expirysnapshots too far apart to say how early
- 2014between Dec 8, 2013 and Apr 20, 2014+1 yearexpiry Dec 5, 2013 → Dec 5, 2014After expiryup to 4 months after expiry
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 xn--l3ca4btt2k1b.com from the who.is WHOIS/RDAP archive, 2012-11-30 to 2024-04-20. Ledger built 2026-09-27.