Renewal History
xn--l3cej5a1au7bdl5d6f8c8b.com
xn--l3cej5a1au7bdl5d6f8c8b.com has been renewed 6 times, usually 1 year at a time. The longest single renewal was 4 years, around 2023, out to 2023. No near-death on record.
Every renewal, newest first
- 2025between Oct 19, 2025 and Nov 21, 2025+1 yearexpiry Oct 24, 2025 → Oct 24, 2026Around expirysnapshots too far apart to say how early
- 2025between Jun 4, 2024 and Sep 13, 2025+1 yearexpiry Oct 24, 2024 → Oct 24, 2025Around expirysnapshots too far apart to say how early
- 2024between Oct 25, 2023 and Jan 3, 2024+1 yearexpiry Oct 24, 2023 → Oct 24, 2024After expiryup to 2 months after expiry
- 2023between Oct 28, 2019 and Oct 25, 2023+4 yearsexpiry Oct 24, 2019 → Oct 24, 2023After expiryup to 48 months after expiry
- 2019between Nov 3, 2016 and Oct 28, 2019+2 yearsexpiry Oct 24, 2017 → Oct 24, 2019Around expirysnapshots too far apart to say how early
- 2016between Oct 6, 2016 and Nov 3, 2016+1 yearexpiry Oct 24, 2016 → Oct 24, 2017Around 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: 22 snapshots of xn--l3cej5a1au7bdl5d6f8c8b.com from the who.is WHOIS/RDAP archive, 2016-08-02 to 2026-04-22. Ledger built 2026-09-27.