dns.pizza

Renewal History

heroku.com

heroku.com has been renewed 5 times, usually 2 years at a time, about 6 weeks before expiry. The longest single renewal was 5 years, around 2011, out to 2019. No near-death on record.

Renewals on record
5
Longest renewal
5 years
Expires
Jun 15, 2027
as of the latest snapshot
Snapshots
413
2011–2026

Every renewal, newest first

  1. 2025
    between May 1, 2025 and May 15, 2025
    +2 yearsexpiry Jun 15, 2025 → Jun 15, 2027Early
    4 to 6 weeks before expiry
  2. 2023
    between May 4, 2023 and May 26, 2023
    +2 yearsexpiry Jun 14, 2023 → Jun 15, 2025Early
    3 to 6 weeks before expiry
  3. 2021
    between Apr 15, 2021 and May 16, 2021
    +2 yearsexpiry Jun 14, 2021 → Jun 14, 2023Early
    1 to 2 months before expiry
  4. 2016
    between Dec 15, 2016 and Dec 24, 2016
    +2 yearsexpiry Jun 15, 2019 → Jun 14, 2021Early
    30 months before expiry
    Transferred: DYNAMIC NETWORK SERVICES, INC → MarkMonitor, Inc.
  5. 2011
    between Sep 13, 2011 and Oct 19, 2011
    +5 yearsexpiry Jun 14, 2014 → Jun 14, 2019Early
    32 to 33 months before expiry
    Transferred: EASYDNS TECHNOLOGIES, INC. → DYNAMIC NETWORK SERVICES, 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: 413 snapshots of heroku.com from the who.is WHOIS/RDAP archive, 2011-09-09 to 2026-05-16. Ledger built 2026-09-27.

Back to heroku.com report