Renewal History
instructure.com
instructure.com has been renewed 7 times, usually 1 year at a time, about 4 weeks before expiry. The longest single renewal was 10 years, around 2016, out to 2024. No near-death on record.
Every renewal, newest first
- 2026between Jan 18, 2026 and Feb 8, 2026+1 yearexpiry Feb 24, 2026 → Feb 24, 2027Early2 to 5 weeks before expiry
- 2025between Jan 6, 2025 and Feb 2, 2025+1 yearexpiry Feb 24, 2025 → Feb 24, 2026Early3 to 7 weeks before expiry
- 2024between Jan 23, 2024 and Jan 26, 2024+1 yearexpiry Feb 24, 2024 → Feb 24, 2025Early4 to 5 weeks before expiryRegistry confirmed an explicit renewal
- 2016between Oct 4, 2013 and Jul 10, 2016+10 yearsexpiry Feb 24, 2014 → Feb 24, 2024Around expirysnapshots too far apart to say how early
- 2013between Nov 13, 2012 and Apr 18, 2013+1 yearexpiry Feb 24, 2013 → Feb 24, 2014Around expirysnapshots too far apart to say how early
- 2012between Sep 28, 2011 and Nov 13, 2012+1 yearexpiry Feb 24, 2012 → Feb 24, 2013Around expirysnapshots too far apart to say how early
- 2011between Aug 14, 2010 and Apr 10, 2011+1 yearexpiry Feb 24, 2011 → Feb 24, 2012Around 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: 352 snapshots of instructure.com from the who.is WHOIS/RDAP archive, 2010-08-14 to 2026-05-12. Ledger built 2026-09-27.