dns.pizza

Renewal History

401k.capital

401k.capital has been renewed 2 times, usually 1 year at a time, about 4 weeks before expiry. It came close to lapsing 3 times.

Renewals on record
2
Longest renewal
1 year
Expires
Feb 7, 2026
as of the latest snapshot
Snapshots
58
2018–2026
Close calls
3
2 drops & re-registration

Every renewal, newest first

  1. 2025
    between Jan 23, 2025 and Feb 24, 2025
    Re-registeredexpiry Nov 9, 2024 → Feb 7, 2026Dropped & re-registered
    a new registration, not a renewal
    Transferred: NameCheap, Inc. → Domain Science Kutatási Szolgáltató Korlátolt Felelősségű TársaságRedemption / pending delete seen
  2. 2023
    between Sep 23, 2023 and Oct 29, 2023
    +1 yearexpiry Nov 9, 2023 → Nov 9, 2024Early
    2 to 7 weeks before expiry
    Redemption / pending delete seen
  3. 2023
    between Sep 8, 2022 and Jan 12, 2023
    +1 yearexpiry Nov 9, 2022 → Nov 9, 2023Around expiry
    snapshots too far apart to say how early
  4. 2021
    between May 29, 2018 and Dec 11, 2021
    Re-registeredexpiry Nov 18, 2018 → Nov 9, 2022Dropped & re-registered
    a new registration, not a renewal
    Transferred: GoDaddy.com, LLC → NameCheap, 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: 58 snapshots of 401k.capital from the who.is WHOIS/RDAP archive, 2018-05-29 to 2026-01-17. Ledger built 2026-09-27.

Back to 401k.capital report