Renewal History

claims-ins.com

claims-ins.com has been renewed 3 times, usually 5 years at a time. It came close to lapsing 2 times.

Renewals on record

Longest renewal

5 years

Expires

Jan 16, 2026

as of the latest snapshot

Snapshots

2011–2025

Close calls

2 drops & re-registration

Every renewal, newest first

2025
between Jan 18, 2024 and Feb 11, 2025
+1 yearexpiry Jan 16, 2025 → Jan 16, 2026Around expiry
snapshots too far apart to say how early
2024
between Aug 6, 2022 and Jan 18, 2024
Re-registeredexpiry Aug 18, 2022 → Jan 16, 2025Dropped & re-registered
a new registration, not a renewal
Transferred: GoDaddy.com, LLC → FastDomain Inc.Registry showed it unregistered
2021
between Dec 23, 2019 and Sep 4, 2021
Re-registeredexpiry Jan 10, 2020 → Aug 18, 2022Dropped & re-registered
a new registration, not a renewal
Transferred: Domain.com, LLC → GoDaddy.com, LLCRegistry showed it unregistered
2019
between Oct 19, 2016 and Jul 17, 2019
+3 yearsexpiry Jan 10, 2017 → Jan 10, 2020Around expiry
snapshots too far apart to say how early
2016
between Jul 5, 2011 and Oct 19, 2016
+5 yearsexpiry Jan 10, 2012 → Jan 10, 2017Around expiry
snapshots too far apart to say how early
Transferred: DOTSTER → Domain.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: 11 snapshots of claims-ins.com from the who.is WHOIS/RDAP archive, 2011-07-05 to 2025-02-11. Ledger built 2026-09-27.

Back to claims-ins.com report