Renewal History

df3.top

df3.top has been renewed once, usually 1 year at a time. No near-death on record.

Renewals on record
1
Longest renewal
1 year
Expires
Jun 2, 2026
as of the latest snapshot
Snapshots
22
2021–2025
Close calls
0
3 drops & re-registration

Every renewal, newest first

  1. 2025
    between Jan 9, 2025 and Aug 29, 2025
    Re-registeredexpiry Mar 9, 2025 → Jun 2, 2026Dropped & re-registered
    a new registration, not a renewal
    Transferred: Chengdu west dimension digital → NameSilo,LLC
  2. 2024
    between Aug 31, 2023 and Apr 9, 2024
    Re-registeredexpiry Oct 18, 2023 → Mar 9, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn) → Chengdu west dimension digital
  3. 2022
    between Jun 25, 2022 and Nov 12, 2022
    Re-registeredexpiry Jun 17, 2023 → Oct 18, 2023Dropped & re-registered
    a new registration, not a renewal
  4. 2022
    between May 7, 2022 and Jun 25, 2022
    +1 yearexpiry Jun 17, 2022 → Jun 17, 2023Around expiry
    snapshots too far apart to say how early
    Registry auto-renew

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: 22 snapshots of df3.top from the who.is WHOIS/RDAP archive, 2021-10-05 to 2025-11-24. Ledger built 2026-09-27.