Renewal History

xn--q3cbw3b7a5gqbc.com

xn--q3cbw3b7a5gqbc.com has been renewed once, usually 1 year at a time. No near-death on record.

Renewals on record
1
Longest renewal
1 year
Expires
Jan 23, 2026
as of the latest snapshot
Snapshots
7
2010–2025
Close calls
0
3 drops & re-registration

Every renewal, newest first

  1. 2025
    between Apr 20, 2024 and Sep 20, 2025
    +1 yearexpiry Jan 23, 2025 → Jan 23, 2026Around expiry
    snapshots too far apart to say how early
  2. 2024
    between Oct 2, 2018 and Apr 20, 2024
    Re-registeredexpiry Sep 24, 2020 → Jan 23, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: GoDaddy.com, LLC → Wild West Domains, LLC
  3. 2018
    between May 16, 2014 and Oct 2, 2018
    Re-registeredexpiry Jun 6, 2014 → Sep 24, 2020Dropped & re-registered
    a new registration, not a renewal
    Transferred: DYNADOT LLC → GoDaddy.com, LLC
  4. 2013
    between Feb 16, 2010 and Dec 24, 2013
    Re-registeredexpiry Mar 19, 2011 → Jun 6, 2014Dropped & re-registered
    a new registration, not a renewal

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: 7 snapshots of xn--q3cbw3b7a5gqbc.com from the who.is WHOIS/RDAP archive, 2010-02-16 to 2025-09-20. Ledger built 2026-09-27.