dns.pizza

Renewal History

oreilly.com

oreilly.com has been renewed 16 times, usually 1 year at a time, about 5 weeks before expiry. The longest single renewal was 4 years, around 2016, out to 2017. No near-death on record.

Renewals on record
16
Longest renewal
4 years
Expires
May 26, 2027
as of the latest snapshot
Snapshots
360
2007–2026

Every renewal, newest first

  1. 2026
    between Apr 15, 2026 and May 14, 2026
    +1 yearexpiry May 26, 2026 → May 26, 2027Early
    2 to 6 weeks before expiry
  2. 2025
    between Apr 10, 2025 and Apr 16, 2025
    +1 yearexpiry May 26, 2025 → May 26, 2026Early
    6 to 7 weeks before expiry
  3. 2024
    between Mar 13, 2024 and Mar 30, 2024
    +1 yearexpiry May 25, 2024 → May 25, 2025Early
    2 months before expiry
  4. 2023
    between Apr 3, 2023 and May 11, 2023
    +1 yearexpiry May 25, 2023 → May 25, 2024Early
    2 to 7 weeks before expiry
  5. 2022
    between Mar 29, 2022 and May 5, 2022
    +1 yearexpiry May 25, 2022 → May 25, 2023Early
    3 to 8 weeks before expiry
  6. 2021
    between Apr 17, 2021 and May 17, 2021
    +1 yearexpiry May 25, 2021 → May 25, 2022Early
    1 to 5 weeks before expiry
  7. 2020
    between Mar 23, 2020 and Apr 24, 2020
    +1 yearexpiry May 26, 2020 → May 26, 2021Early
    1 to 2 months before expiry
  8. 2019
    between Apr 30, 2019 and May 30, 2019
    +1 yearexpiry May 26, 2019 → May 26, 2020Around expiry
    snapshots too far apart to say how early
  9. 2018
    between Apr 10, 2018 and May 1, 2018
    +1 yearexpiry May 26, 2018 → May 26, 2019Early
    4 to 7 weeks before expiry
  10. 2017
    between Apr 14, 2017 and May 14, 2017
    +1 yearexpiry May 26, 2017 → May 26, 2018Early
    2 to 6 weeks before expiry
  11. 2016
    between Sep 20, 2012 and Aug 9, 2016
    +4 yearsexpiry May 26, 2013 → May 26, 2017Around expiry
    snapshots too far apart to say how early
  12. 2012
    between May 26, 2012 and Jun 1, 2012
    +1 yearexpiry May 26, 2012 → May 26, 2013Around expiry
    snapshots too far apart to say how early
  13. 2011
    between May 2, 2011 and Jul 17, 2011
    +1 yearexpiry May 25, 2011 → May 26, 2012Around expiry
    snapshots too far apart to say how early
  14. 2010
    between May 14, 2010 and Jun 3, 2010
    +1 yearexpiry May 25, 2010 → May 25, 2011Around expiry
    snapshots too far apart to say how early
  15. 2009
    between Apr 15, 2009 and May 8, 2009
    +1 yearexpiry May 25, 2009 → May 25, 2010Early
    2 to 6 weeks before expiry
  16. 2008
    between Apr 1, 2008 and Apr 6, 2008
    +1 yearexpiry May 25, 2008 → May 25, 2009Early
    7 to 8 weeks before expiry

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: 360 snapshots of oreilly.com from the who.is WHOIS/RDAP archive, 2007-07-17 to 2026-05-17. Ledger built 2026-09-27.

Back to oreilly.com report