Renewal History
quickdataservices.com
quickdataservices.com has been renewed 5 times, usually 1 year at a time. The longest single renewal was 4 years, around 2021, out to 2021. No near-death on record.
Every renewal, newest first
- 2024between Aug 1, 2022 and Feb 2, 2024+1 yearexpiry Apr 4, 2023 → Apr 4, 2024Around expirysnapshots too far apart to say how early
- 2022between Sep 7, 2021 and Aug 1, 2022+1 yearexpiry Apr 4, 2022 → Apr 4, 2023Around expirysnapshots too far apart to say how early
- 2021between Mar 27, 2021 and Sep 7, 2021+1 yearexpiry Apr 4, 2021 → Apr 4, 2022Around expirysnapshots too far apart to say how early
- 2021between Aug 5, 2016 and Mar 27, 2021+4 yearsexpiry Apr 4, 2017 → Apr 4, 2021Around expirysnapshots too far apart to say how early
- 2016between Feb 17, 2010 and Aug 5, 2016Re-registeredexpiry Jan 17, 2011 → Apr 4, 2017Dropped & re-registereda new registration, not a renewal
- 2010between Aug 24, 2009 and Feb 17, 2010+1 yearexpiry Jan 17, 2010 → Jan 17, 2011Around 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 quickdataservices.com from the who.is WHOIS/RDAP archive, 2009-08-24 to 2024-04-26. Ledger built 2026-09-27.