Renewal History
telegram.network
telegram.network has been renewed 2 times, usually 4 years at a time. No near-death on record.
Every renewal, newest first
- 2026between Aug 24, 2024 and Jan 15, 2026+1 yearexpiry Jul 6, 2025 → Jul 6, 2026Around expirysnapshots too far apart to say how early
- 2024between Jun 9, 2021 and Aug 24, 2024+4 yearsexpiry Jul 6, 2021 → Jul 6, 2025Around expirysnapshots too far apart to say how earlyTransferred: Uniregistrar Corp → Porkbun LLC
- 2021between Aug 22, 2019 and Jun 9, 2021Re-registeredexpiry Apr 18, 2020 → Jul 6, 2021Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → Uniregistrar Corp
- 2019between Jan 23, 2019 and Aug 22, 2019Re-registeredexpiry Jan 28, 2019 → Apr 18, 2020Dropped & re-registereda new registration, not a renewalTransferred: eNom, LLC → GoDaddy.com, LLC
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: 7 snapshots of telegram.network from the who.is WHOIS/RDAP archive, 2018-10-16 to 2026-01-15. Ledger built 2026-09-27.