Renewal History

xn--c3ca1fba9ewem0d3b.com

xn--c3ca1fba9ewem0d3b.com has been renewed 4 times, usually 1 year at a time. The longest single renewal was 3 years, around 2017, out to 2017. No near-death on record.

Renewals on record

Longest renewal

3 years

Expires

May 5, 2025

as of the latest snapshot

Snapshots

2013–2024

Close calls

1 drop & re-registration

Every renewal, newest first

2024
between Mar 1, 2021 and Aug 16, 2024
Re-registeredexpiry Nov 26, 2021 → May 5, 2025Dropped & re-registered
a new registration, not a renewal
Transferred: DYNADOT LLC → NAMECHEAP INC
2020
between Mar 30, 2020 and Jun 25, 2020
+1 yearexpiry Nov 26, 2020 → Nov 26, 2021Early
5 to 8 months before expiry
Transferred: Name.com, Inc. → DYNADOT LLC
2020
between Dec 5, 2018 and Jan 9, 2020
+2 yearsexpiry Nov 26, 2018 → Nov 26, 2020After expiry
up to 13 months after expiry
Registry auto-renew
2018
between Oct 8, 2017 and May 10, 2018
+1 yearexpiry Nov 26, 2017 → Nov 26, 2018Around expiry
snapshots too far apart to say how early
Registry auto-renew
2017
between May 27, 2014 and Apr 28, 2017
+3 yearsexpiry Nov 26, 2014 → Nov 26, 2017Around expiry
snapshots 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: 26 snapshots of xn--c3ca1fba9ewem0d3b.com from the who.is WHOIS/RDAP archive, 2013-11-26 to 2024-08-16. Ledger built 2026-09-27.

Back to xn--c3ca1fba9ewem0d3b.com report