Renewal History
belbenclaims.com
belbenclaims.com has been renewed 5 times, usually 1 year at a time, about 10 months before expiry. The longest single renewal was 3 years, around 2017, out to 2019. No near-death on record.
Every renewal, newest first
- 2024between Jan 8, 2024 and Sep 3, 2024Re-registeredexpiry Jan 18, 2024 → Apr 9, 2025Dropped & re-registereda new registration, not a renewalTransferred: ENOM, INC. → Network Solutions, LLC
- 2023between Dec 8, 2022 and Mar 22, 2023+1 yearexpiry Jan 18, 2023 → Jan 18, 2024Around expirysnapshots too far apart to say how early
- 2022between Jan 12, 2022 and Jan 14, 2022+1 yearexpiry Jan 18, 2022 → Jan 18, 2023Early4 to 6 days before expiryRegistry confirmed an explicit renewal
- 2019between Jun 14, 2019 and Jun 20, 2019+1 yearexpiry Jan 18, 2021 → Jan 18, 2022Early19 months before expiryTransferred: Domain.com, LLC → ENOM, INC.
- 2019between May 17, 2018 and Apr 17, 2019+2 yearsexpiry Jan 18, 2019 → Jan 18, 2021Around expirysnapshots too far apart to say how early
- 2017between Mar 2, 2014 and Jan 13, 2017+3 yearsexpiry Jan 18, 2016 → Jan 18, 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: 27 snapshots of belbenclaims.com from the who.is WHOIS/RDAP archive, 2014-01-21 to 2024-09-03. Ledger built 2026-09-27.