dns.pizza

Renewal History

spacloudflare.com

spacloudflare.com 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
Jul 30, 2026
as of the latest snapshot
Snapshots
24
2020–2026
Close calls
2
2 drops & re-registration

Every renewal, newest first

  1. 2025
    between Jun 16, 2025 and Sep 15, 2025
    Re-registeredexpiry May 7, 2025 → Jul 30, 2026Dropped & re-registered
    a new registration, not a renewal
    Transferred: LWS dba Ligne Web Services → Dynadot IncRedemption / pending delete seen
  2. 2024
    between Jan 14, 2023 and Oct 1, 2024
    Re-registeredexpiry Feb 17, 2023 → May 7, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: NAMECHEAP INC → LWS dba Ligne Web ServicesRedemption / pending delete seen
  3. 2022
    between Jan 1, 2022 and Jul 20, 2022
    +1 yearexpiry Feb 17, 2022 → Feb 17, 2023Around expiry
    snapshots too far apart to say how early
  4. 2021
    between Dec 24, 2020 and Mar 12, 2021
    +1 yearexpiry Feb 17, 2021 → Feb 17, 2022Around expiry
    snapshots too far apart to say how early
    Transferred: GoDaddy.com, LLC → NAMECHEAP INC

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: 24 snapshots of spacloudflare.com from the who.is WHOIS/RDAP archive, 2020-08-17 to 2026-05-31. Ledger built 2026-09-27.

Back to spacloudflare.com report