Renewal History
finance.solutions
finance.solutions has been renewed once, usually 4 years at a time. It came close to lapsing 4 times.
Every renewal, newest first
- 2024between May 5, 2024 and May 17, 2024Re-registeredexpiry Feb 26, 2024 → May 16, 2025Dropped & re-registereda new registration, not a renewalTransferred: Sav.com, LLC - 25 → Sav.com, LLCRedemption / pending delete seen
- 2024between Feb 14, 2023 and May 5, 2024Re-registeredexpiry Dec 10, 2022 → Feb 26, 2024Dropped & re-registereda new registration, not a renewalTransferred: Uniregistrar Corp → Sav.com, LLC - 25Redemption / pending delete seen
- 2023between Oct 24, 2018 and Feb 14, 2023Re-registeredexpiry Mar 22, 2019 → Dec 10, 2022Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → Uniregistrar CorpRedemption / pending delete seen
- 2018between Apr 16, 2014 and May 3, 2018+4 yearsexpiry Mar 22, 2015 → Mar 22, 2019Around expirysnapshots too far apart to say how earlyTransferred: Name.com LLC → GoDaddy.com, LLCRegistry auto-renewRedemption / pending delete seen
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: 6 snapshots of finance.solutions from the who.is WHOIS/RDAP archive, 2014-04-16 to 2024-05-17. Ledger built 2026-09-27.