dns.pizza

Renewal History

onmicrosoft.com

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

Renewals on record
16
Longest renewal
2 years
Expires
Feb 3, 2027
as of the latest snapshot
Snapshots
2,141
2011–2026
Close calls
0
3 drops & re-registration

Every renewal, newest first

  1. Jan 2, 2026
    +1 yearexpiry Feb 3, 2026 → Feb 3, 2027Early
    5 weeks before expiry
  2. 2025
    between Dec 30, 2024 and Jan 2, 2025
    +1 yearexpiry Feb 3, 2025 → Feb 3, 2026Early
    5 weeks before expiry
  3. 2024
    between Dec 28, 2023 and Jan 2, 2024
    +1 yearexpiry Feb 3, 2024 → Feb 3, 2025Early
    5 weeks before expiry
  4. Jan 2, 2023
    +1 yearexpiry Feb 3, 2023 → Feb 3, 2024Early
    5 weeks before expiry
  5. 2022
    between Jan 1, 2022 and Jan 3, 2022
    +1 yearexpiry Feb 3, 2022 → Feb 3, 2023Early
    4 to 5 weeks before expiry
  6. 2021
    between Dec 30, 2020 and Jan 2, 2021
    +1 yearexpiry Feb 2, 2021 → Feb 2, 2022Early
    4 to 5 weeks before expiry
  7. 2020
    between Dec 29, 2019 and Jan 6, 2020
    +1 yearexpiry Feb 2, 2020 → Feb 2, 2021Early
    4 to 5 weeks before expiry
  8. 2019
    between Dec 24, 2018 and Jan 6, 2019
    +1 yearexpiry Feb 2, 2019 → Feb 2, 2020Early
    4 to 6 weeks before expiry
  9. 2018
    between Dec 26, 2017 and Jan 6, 2018
    +1 yearexpiry Feb 2, 2018 → Feb 2, 2019Early
    4 to 5 weeks before expiry
  10. 2017
    between Dec 30, 2016 and Jan 15, 2017
    +1 yearexpiry Feb 2, 2017 → Feb 2, 2018Early
    3 to 5 weeks before expiry
  11. 2016
    between May 27, 2014 and Jun 18, 2016
    +2 yearsexpiry Feb 2, 2015 → Feb 2, 2017Around expiry
    snapshots too far apart to say how early
  12. 2014
    between Dec 30, 2013 and Jan 3, 2014
    +1 yearexpiry Feb 2, 2014 → Feb 2, 2015Early
    4 to 5 weeks before expiry
  13. 2013
    between Jan 1, 2013 and Jan 3, 2013
    +1 yearexpiry Feb 2, 2013 → Feb 2, 2014Early
    4 to 5 weeks before expiry
  14. 2012
    between Sep 22, 2012 and Oct 30, 2012
    Re-registeredexpiry Dec 21, 2013 → Feb 2, 2013Dropped & re-registered
    a new registration, not a renewal
  15. Sep 22, 2012
    +1 yearexpiry Feb 3, 2013 → Dec 21, 2013Early
    4 months before expiry
  16. 2012
    between Sep 4, 2012 and Sep 6, 2012
    Re-registeredexpiry Dec 21, 2013 → Feb 2, 2013Dropped & re-registered
    a new registration, not a renewal
  17. Sep 4, 2012
    +1 yearexpiry Feb 3, 2013 → Dec 21, 2013Early
    5 months before expiry
  18. 2012
    between Jul 29, 2012 and Jul 31, 2012
    Re-registeredexpiry Dec 21, 2013 → Feb 2, 2013Dropped & re-registered
    a new registration, not a renewal
  19. Jul 29, 2012
    +1 yearexpiry Feb 3, 2013 → Dec 21, 2013Early
    6 months 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: 2,141 snapshots of onmicrosoft.com from the who.is WHOIS/RDAP archive, 2011-01-09 to 2026-05-12. Ledger built 2026-09-27.

Back to onmicrosoft.com report