Renewal History
dan.hosting
dan.hosting has been renewed 6 times, usually 1 year at a time. No near-death on record.
Every renewal, newest first
- 2026between Jan 14, 2026 and Feb 17, 2026+1 yearexpiry Feb 10, 2026 → Feb 10, 2027Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2025between Feb 5, 2025 and Feb 19, 2025+1 yearexpiry Feb 10, 2025 → Feb 10, 2026Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2024between Feb 9, 2024 and Mar 15, 2024+1 yearexpiry Feb 10, 2024 → Feb 10, 2025Around expirysnapshots too far apart to say how early
- 2023between Dec 7, 2022 and Apr 6, 2023+1 yearexpiry Feb 10, 2023 → Feb 10, 2024Around expirysnapshots too far apart to say how early
- 2022between Oct 20, 2021 and Dec 7, 2022+1 yearexpiry Feb 10, 2022 → Feb 10, 2023Around expirysnapshots too far apart to say how early
- 2021between Sep 10, 2020 and Aug 18, 2021+1 yearexpiry Feb 10, 2021 → Feb 10, 2022Around 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: 92 snapshots of dan.hosting from the who.is WHOIS/RDAP archive, 2020-09-10 to 2026-05-14. Ledger built 2026-09-27.