Renewal History
telegramme228.com
telegramme228.com has been renewed 6 times, usually 1 year at a time. The longest single renewal was 5 years, around 2018, out to 2018. No near-death on record.
Every renewal, newest first
- 2026between Apr 6, 2024 and Feb 2, 2026+2 yearsexpiry Oct 29, 2024 → Oct 29, 2026Around expirysnapshots too far apart to say how earlyTransferred: LWS dba Ligne Web Services → Ligne Web Services SAS dba LWS
- 2023between Jan 10, 2023 and Nov 30, 2023+1 yearexpiry Oct 29, 2023 → Oct 29, 2024Around expirysnapshots too far apart to say how early
- 2023between Jan 4, 2022 and Jan 10, 2023+1 yearexpiry Oct 29, 2022 → Oct 29, 2023Around expirysnapshots too far apart to say how earlyTransferred: OVH, SAS → LWS dba Ligne Web Services
- 2022between Jun 30, 2019 and Jan 4, 2022+3 yearsexpiry Oct 29, 2019 → Oct 29, 2022Around expirysnapshots too far apart to say how early
- 2019between Jun 16, 2018 and Jun 30, 2019+1 yearexpiry Oct 29, 2018 → Oct 29, 2019Around expirysnapshots too far apart to say how early
- 2018between Dec 10, 2012 and Jun 16, 2018+5 yearsexpiry Oct 29, 2013 → Oct 29, 2018Around expirysnapshots 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: 9 snapshots of telegramme228.com from the who.is WHOIS/RDAP archive, 2012-12-10 to 2026-02-02. Ledger built 2026-09-27.