dns.pizza

Renewal History

xn--72c0bbb6bb2c0cmc3wd.com

xn--72c0bbb6bb2c0cmc3wd.com has been renewed 8 times, usually 1 year at a time, about 4 months before expiry. The longest single renewal was 2 years, around 2016, out to 2017. No near-death on record.

Renewals on record
8
Longest renewal
2 years
Expires
Aug 3, 2023
as of the latest snapshot
Snapshots
73
2010–2022
Close calls
0
2 drops & re-registration

Every renewal, newest first

  1. 2022
    between Jun 26, 2022 and Aug 4, 2022
    Re-registeredexpiry May 15, 2022 → Aug 3, 2023Dropped & re-registered
    a new registration, not a renewal
    Transferred: Name.com, Inc. → PDR Ltd. d/b/a PublicDomainRegistry.com
  2. 2021
    between Mar 26, 2020 and Nov 19, 2021
    +2 yearsexpiry May 15, 2020 → May 15, 2022Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  3. 2019
    between Nov 29, 2018 and Jun 16, 2019
    +1 yearexpiry May 15, 2019 → May 15, 2020Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  4. 2018
    between Oct 8, 2017 and Oct 9, 2018
    +1 yearexpiry May 15, 2018 → May 15, 2019Around expiry
    snapshots too far apart to say how early
  5. 2017
    between Apr 28, 2017 and Aug 13, 2017
    +1 yearexpiry May 15, 2017 → May 15, 2018Around expiry
    snapshots too far apart to say how early
  6. 2016
    between Jun 5, 2014 and Nov 8, 2016
    +2 yearsexpiry May 15, 2015 → May 15, 2017Around expiry
    snapshots too far apart to say how early
  7. 2014
    between Jan 9, 2013 and May 19, 2014
    Re-registeredexpiry Feb 25, 2014 → May 15, 2015Dropped & re-registered
    a new registration, not a renewal
  8. 2012
    between Nov 7, 2012 and Nov 9, 2012
    +1 yearexpiry Feb 25, 2013 → Feb 25, 2014Early
    4 months before expiry
  9. 2012
    between Mar 25, 2011 and Nov 4, 2012
    +1 yearexpiry Feb 25, 2012 → Feb 25, 2013Around expiry
    snapshots too far apart to say how early
  10. 2011
    between Dec 6, 2010 and Mar 25, 2011
    +1 yearexpiry Feb 25, 2011 → Feb 25, 2012Around 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: 73 snapshots of xn--72c0bbb6bb2c0cmc3wd.com from the who.is WHOIS/RDAP archive, 2010-04-16 to 2022-11-12. Ledger built 2026-09-27.

Back to xn--72c0bbb6bb2c0cmc3wd.com report