dns.pizza

Renewal History

r4d.top

r4d.top has been renewed 2 times, usually 1 year at a time. It came close to lapsing 2 times.

Renewals on record
2
Longest renewal
1 year
Expires
Dec 5, 2026
as of the latest snapshot
Snapshots
18
2021–2026
Close calls
2
2 drops & re-registration

Every renewal, newest first

  1. 2025
    between Dec 2, 2025 and Dec 16, 2025
    +1 yearexpiry Dec 5, 2025 → Dec 5, 2026Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  2. 2025
    between Aug 31, 2023 and May 28, 2025
    Re-registeredexpiry Nov 25, 2023 → Dec 5, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: PDR Ltd → Namecheap Inc.Registry showed it unregistered
  3. 2022
    between Aug 7, 2022 and Dec 23, 2022
    Re-registeredexpiry Jun 17, 2022 → Nov 25, 2023Dropped & re-registered
    a new registration, not a renewal
    Transferred: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn) → PDR LtdRedemption / pending delete seenRegistry showed it unregistered
  4. 2022
    between Mar 22, 2022 and Jun 22, 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: 18 snapshots of r4d.top from the who.is WHOIS/RDAP archive, 2021-09-25 to 2026-01-10. Ledger built 2026-09-27.

Back to r4d.top report