Renewal History
secureweb-services.com
secureweb-services.com has been renewed 6 times, usually 1 year at a time. The longest single renewal was 4 years, around 2016, out to 2017. No near-death on record.
Every renewal, newest first
- 2024between Apr 22, 2024 and Nov 18, 2024+1 yearexpiry Jul 29, 2024 → Jul 29, 2025Around expirysnapshots too far apart to say how early
- 2024between Jan 24, 2020 and Apr 22, 2024+4 yearsexpiry Jul 29, 2020 → Jul 29, 2024Around expirysnapshots too far apart to say how early
- 2020between Nov 22, 2018 and Jan 24, 2020+1 yearexpiry Jul 29, 2019 → Jul 29, 2020Around expirysnapshots too far apart to say how early
- 2018between Jul 12, 2018 and Nov 22, 2018+1 yearexpiry Jul 29, 2018 → Jul 29, 2019Around expirysnapshots too far apart to say how earlyTransferred: Astutium Limited → Netistrar Ltd
- 2017between Sep 20, 2016 and Dec 17, 2017+1 yearexpiry Jul 29, 2017 → Jul 29, 2018Around expirysnapshots too far apart to say how early
- 2016between May 28, 2013 and Sep 20, 2016+4 yearsexpiry Jul 29, 2013 → Jul 29, 2017Around 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: 8 snapshots of secureweb-services.com from the who.is WHOIS/RDAP archive, 2013-05-28 to 2024-11-18. Ledger built 2026-09-27.