dns.pizza

Renewal History

telegram.cat

telegram.cat 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
Sep 3, 2026
as of the latest snapshot
Snapshots
9
2016–2026
Close calls
2
2 drops & re-registration

Every renewal, newest first

  1. 2026
    between Aug 12, 2025 and Apr 10, 2026
    +1 yearexpiry Sep 3, 2025 → Sep 3, 2026Around expiry
    snapshots too far apart to say how early
    Transferred: Hosting Concepts B.V. d/b/a Registrar.eu → Openprovider
  2. 2025
    between Jul 14, 2019 and Aug 9, 2025
    Re-registeredexpiry Mar 22, 2020 → Sep 3, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: Nominalia → Openprovider
  3. 2019
    between Aug 22, 2018 and Jul 14, 2019
    Re-registeredexpiry Jun 30, 2018 → Mar 22, 2020Dropped & re-registered
    a new registration, not a renewal
    Transferred: Cronon AG → NominaliaRedemption / pending delete seen
  4. 2018
    between Nov 3, 2016 and Aug 22, 2018
    +1 yearexpiry Jun 30, 2017 → Jun 30, 2018Around expiry
    snapshots too far apart to say how early
    Redemption / pending delete seen

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: 9 snapshots of telegram.cat from the who.is WHOIS/RDAP archive, 2016-11-03 to 2026-04-10. Ledger built 2026-09-27.

Back to telegram.cat report