Renewal History

xn--72c9ap2a1b7c3cd3f.com

xn--72c9ap2a1b7c3cd3f.com has been renewed 3 times, usually 2 years at a time. The longest single renewal was 4 years, around 2023, out to 2024. No near-death on record.

Renewals on record
3
Longest renewal
4 years
Expires
Jun 29, 2024
as of the latest snapshot
Snapshots
11
2010–2024
Close calls
0
1 drop & re-registration

Every renewal, newest first

  1. 2023
    between Dec 16, 2019 and Dec 30, 2023
    +4 yearsexpiry Jun 29, 2020 → Jun 29, 2024Around expiry
    snapshots too far apart to say how early
  2. 2019
    between May 28, 2014 and Oct 17, 2019
    Re-registeredexpiry Mar 11, 2015 → Jun 29, 2020Dropped & re-registered
    a new registration, not a renewal
    Transferred: Name.com, Inc. → GoDaddy.com, LLC
  3. 2014
    between Dec 12, 2012 and May 28, 2014
    +2 yearsexpiry Mar 11, 2013 → Mar 11, 2015Around expiry
    snapshots too far apart to say how early
  4. 2012
    between Jul 5, 2010 and Feb 23, 2012
    +2 yearsexpiry Mar 11, 2011 → Mar 11, 2013Around 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: 11 snapshots of xn--72c9ap2a1b7c3cd3f.com from the who.is WHOIS/RDAP archive, 2010-02-18 to 2024-04-23. Ledger built 2026-09-27.