Renewal History
npmjs.com
npmjs.com has been renewed 6 times, usually 2 years at a time, about 17 months before expiry. The longest single renewal was 7 years, around 2019, out to 2029. No near-death on record.
Every renewal, newest first
- 2023between Feb 16, 2023 and Feb 24, 2023+2 yearsexpiry Mar 19, 2029 → Mar 19, 2031Early73 months before expiryTransferred: Amazon Registrar, Inc. → MarkMonitor, Inc.
- 2019between Nov 14, 2019 and Dec 5, 2019+7 yearsexpiry Mar 19, 2022 → Mar 19, 2029Early27 to 28 months before expiryRegistry confirmed an explicit renewal
- 2019between Oct 11, 2019 and Nov 14, 2019+1 yearexpiry Mar 19, 2021 → Mar 19, 2022Early16 to 17 months before expiryTransferred: Oracle Corporation → Amazon Registrar, Inc.
- 2019between Feb 20, 2019 and Mar 13, 2019+2 yearsexpiry Mar 19, 2019 → Mar 19, 2021Early1 to 4 weeks before expiry
- 2017between Feb 21, 2017 and Mar 5, 2017+2 yearsexpiry Mar 19, 2017 → Mar 19, 2019Early2 to 4 weeks before expiry
- 2016between Feb 26, 2014 and Jul 9, 2016+2 yearsexpiry Mar 19, 2015 → Mar 19, 2017Around expirysnapshots too far apart to say how earlyTransferred: Name.com, Inc. → DYNAMIC NETWORK SERVICES, INC
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: 328 snapshots of npmjs.com from the who.is WHOIS/RDAP archive, 2014-02-26 to 2026-05-19. Ledger built 2026-09-27.