dns.pizza

Renewal History

xn--m3cm4a2c6ayg.com

xn--m3cm4a2c6ayg.com has been renewed 2 times, usually 1 year at a time. It came close to lapsing once.

Renewals on record
2
Longest renewal
1 year
Expires
Dec 1, 2019
as of the latest snapshot
Snapshots
20
2013–2019
Close calls
1
1 drop & re-registration

Every renewal, newest first

  1. 2019
    between Jul 9, 2018 and Jan 15, 2019
    +1 yearexpiry Dec 1, 2018 → Dec 1, 2019Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  2. 2018
    between Oct 8, 2017 and Jul 9, 2018
    +1 yearexpiry Dec 1, 2017 → Dec 1, 2018Around expiry
    snapshots too far apart to say how early
  3. 2017
    between May 20, 2014 and Apr 25, 2017
    Re-registeredexpiry Sep 5, 2014 → Dec 1, 2017Dropped & re-registered
    a new registration, not a renewal
    Transferred: Need Servers, Inc → Name.com, Inc.Registry showed it unregistered

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: 20 snapshots of xn--m3cm4a2c6ayg.com from the who.is WHOIS/RDAP archive, 2013-09-05 to 2019-01-15. Ledger built 2026-09-27.

Back to xn--m3cm4a2c6ayg.com report