dns.pizza

Renewal History

bptracking.com

bptracking.com has been renewed 8 times, usually 1 year at a time. The longest single renewal was 5 years, around 2019, out to 2020. It came close to lapsing 2 times.

Renewals on record
8
Longest renewal
5 years
Expires
Aug 20, 2026
as of the latest snapshot
Snapshots
78
2010–2026
Close calls
2
1 drop & re-registration

Every renewal, newest first

  1. 2025
    between Jun 4, 2025 and Aug 29, 2025
    Re-registeredexpiry Apr 19, 2025 → Aug 20, 2026Dropped & re-registered
    a new registration, not a renewal
    Transferred: Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA → Cloudflare, Inc.Redemption / pending delete seenRegistry showed it unregistered
  2. 2024
    between Dec 13, 2023 and Jun 19, 2024
    +1 yearexpiry Apr 19, 2024 → Apr 19, 2025Around expiry
    snapshots too far apart to say how early
    Redemption / pending delete seen
  3. 2023
    between Dec 26, 2022 and Jun 21, 2023
    +1 yearexpiry Apr 19, 2023 → Apr 19, 2024Around expiry
    snapshots too far apart to say how early
  4. 2022
    between Mar 26, 2022 and Dec 26, 2022
    +1 yearexpiry Apr 19, 2022 → Apr 19, 2023Around expiry
    snapshots too far apart to say how early
  5. 2022
    between Mar 12, 2021 and Mar 26, 2022
    +1 yearexpiry Apr 19, 2021 → Apr 19, 2022Around expiry
    snapshots too far apart to say how early
  6. 2021
    between Sep 30, 2019 and Mar 12, 2021
    +1 yearexpiry Apr 19, 2020 → Apr 19, 2021Around expiry
    snapshots too far apart to say how early
    Transferred: Binero AB → Ascio Technologies, Inc
  7. 2019
    between Apr 9, 2014 and Sep 30, 2019
    +5 yearsexpiry Apr 19, 2015 → Apr 19, 2020Around expiry
    snapshots too far apart to say how early
  8. 2014
    between Aug 31, 2011 and Apr 9, 2014
    +3 yearsexpiry Apr 19, 2012 → Apr 19, 2015Around expiry
    snapshots too far apart to say how early
  9. 2011
    between Aug 17, 2010 and Aug 31, 2011
    +1 yearexpiry Apr 19, 2011 → Apr 19, 2012Around expiry
    snapshots too far apart to say how early

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: 78 snapshots of bptracking.com from the who.is WHOIS/RDAP archive, 2010-08-17 to 2026-05-30. Ledger built 2026-09-27.

Back to bptracking.com report