Renewal History
xn--q3cax8dd1l2a.com
xn--q3cax8dd1l2a.com has been renewed 5 times, usually 1 year at a time. The longest single renewal was 4 years, around 2018, out to 2019. No near-death on record.
Every renewal, newest first
- 2025between Nov 19, 2018 and Jul 16, 2025Re-registeredexpiry May 18, 2019 → Jul 14, 2026Dropped & re-registereda new registration, not a renewal
- 2018between May 30, 2014 and May 14, 2018+4 yearsexpiry May 18, 2015 → May 18, 2019Around expirysnapshots too far apart to say how earlyTransferred: Name.com, Inc. → DYNADOT LLC
- 2014between Apr 28, 2014 and May 21, 2014+1 yearexpiry May 18, 2014 → May 18, 2015Around expirysnapshots too far apart to say how earlyRegistry confirmed an explicit renewal
- 2013between Mar 19, 2013 and May 22, 2013+1 yearexpiry May 18, 2013 → May 18, 2014Around expirysnapshots too far apart to say how early
- 2012between Nov 1, 2011 and Dec 26, 2012+1 yearexpiry May 18, 2012 → May 18, 2013Around expirysnapshots too far apart to say how early
- 2011between Mar 23, 2011 and Jun 23, 2011+1 yearexpiry May 18, 2011 → May 18, 2012Around 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: 31 snapshots of xn--q3cax8dd1l2a.com from the who.is WHOIS/RDAP archive, 2011-03-23 to 2025-07-16. Ledger built 2026-09-27.