Renewal History
tomcast.net
tomcast.net has been renewed 7 times, usually 1 year at a time. No near-death on record.
Every renewal, newest first
- 2026between Jan 19, 2025 and May 28, 2026+1 yearexpiry Jul 29, 2025 → Jul 29, 2026Around expirysnapshots too far apart to say how early
- 2024between Feb 19, 2024 and Nov 26, 2024+1 yearexpiry Jul 29, 2024 → Jul 29, 2025Around expirysnapshots too far apart to say how earlyTransferred: GoDaddy.com, LLC → Media Elite Holdings Limited
- 2023between Jun 5, 2023 and Nov 24, 2023+1 yearexpiry Jul 29, 2023 → Jul 29, 2024Around expirysnapshots too far apart to say how early
- 2022between Jul 1, 2022 and Jul 31, 2022+1 yearexpiry Jul 29, 2022 → Jul 29, 2023Around expirysnapshots too far apart to say how early
- 2021between Jul 6, 2021 and Aug 8, 2021+1 yearexpiry Jul 29, 2021 → Jul 29, 2022Around expirysnapshots too far apart to say how early
- 2020between May 31, 2020 and Aug 17, 2020+1 yearexpiry Jul 29, 2020 → Jul 29, 2021Around expirysnapshots too far apart to say how early
- 2019between May 17, 2019 and Sep 8, 2019Re-registeredexpiry Apr 19, 2019 → Jul 29, 2020Dropped & re-registereda new registration, not a renewalTransferred: NameKing.com, Inc. → GoDaddy.com, LLC
- 2018between Feb 22, 2018 and Apr 27, 2018+1 yearexpiry Apr 19, 2018 → Apr 19, 2019Around 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: 53 snapshots of tomcast.net from the who.is WHOIS/RDAP archive, 2017-04-18 to 2026-05-28. Ledger built 2026-09-27.