dns.pizza

Renewal History

momnx.com

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

Renewals on record
15
Longest renewal
2 years
Expires
Apr 7, 2026
as of the latest snapshot
Snapshots
98
2009–2025

Every renewal, newest first

  1. 2025
    between Sep 25, 2024 and Nov 14, 2025
    +1 yearexpiry Apr 7, 2025 → Apr 7, 2026Around expiry
    snapshots too far apart to say how early
  2. 2024
    between Dec 29, 2023 and Jul 14, 2024
    +1 yearexpiry Apr 7, 2024 → Apr 7, 2025Around expiry
    snapshots too far apart to say how early
  3. 2023
    between Mar 2, 2023 and Apr 18, 2023
    +1 yearexpiry Apr 7, 2023 → Apr 7, 2024Around expiry
    snapshots too far apart to say how early
  4. 2022
    between Feb 14, 2022 and May 4, 2022
    +1 yearexpiry Apr 7, 2022 → Apr 7, 2023Around expiry
    snapshots too far apart to say how early
  5. 2021
    between Feb 22, 2021 and Mar 31, 2021
    +1 yearexpiry Apr 7, 2021 → Apr 7, 2022Early
    1 to 6 weeks before expiry
  6. 2020
    between Apr 8, 2020 and May 13, 2020
    +1 yearexpiry Apr 7, 2020 → Apr 7, 2021In grace period
    up to 5 weeks after expiry
  7. 2019
    between Mar 11, 2019 and Apr 14, 2019
    +1 yearexpiry Apr 7, 2019 → Apr 7, 2020Around expiry
    snapshots too far apart to say how early
  8. 2018
    between Nov 14, 2016 and Aug 21, 2018
    +2 yearsexpiry Apr 7, 2017 → Apr 7, 2019Around expiry
    snapshots too far apart to say how early
    Transferred: ENOM, INC. → NAMECHEAP INCRegistry confirmed an explicit renewal
  9. 2016
    between May 17, 2014 and Nov 14, 2016
    +2 yearsexpiry Apr 7, 2015 → Apr 7, 2017Around expiry
    snapshots too far apart to say how early
  10. 2014
    between Feb 25, 2014 and May 8, 2014
    +1 yearexpiry Apr 7, 2014 → Apr 7, 2015Around expiry
    snapshots too far apart to say how early
  11. 2013
    between Feb 1, 2013 and Apr 13, 2013
    +1 yearexpiry Apr 7, 2013 → Apr 7, 2014Around expiry
    snapshots too far apart to say how early
  12. 2012
    between Mar 1, 2012 and Aug 16, 2012
    +1 yearexpiry Apr 7, 2012 → Apr 7, 2013Around expiry
    snapshots too far apart to say how early
  13. 2011
    between Dec 27, 2010 and Mar 20, 2011
    +1 yearexpiry Apr 7, 2011 → Apr 7, 2012Early
    1 to 3 months before expiry
  14. 2010
    between Jul 23, 2009 and Mar 8, 2010
    +1 yearexpiry Apr 7, 2010 → Apr 7, 2011Early
    1 to 8 months before expiry
  15. 2009
    between Jan 23, 2009 and Jul 23, 2009
    +1 yearexpiry Apr 7, 2009 → Apr 7, 2010Around expiry
    snapshots 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: 98 snapshots of momnx.com from the who.is WHOIS/RDAP archive, 2009-01-23 to 2025-12-21. Ledger built 2026-09-27.

Back to momnx.com report