npmjs.com
IPv6
Measured 2026-11-01 10:31 UTC · aaaa.botWebsite, mail and DNS all work over IPv6.
Both published IPv6 addresses accepted a connection when we tried them.
- ✓ npmjs.com answers (2 of 2 addresses)
- ✓ www.npmjs.com answers (2 of 2)
- ✓ Mail: 5 of 5 servers have IPv6
- ✓ Nameservers: 2 of 2 have IPv6
Details: published addresses and what answered
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 403.
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| npmjs.com | Published2606:4700::6811:86752606:4700::6811:8775 | Answers when we connect✓ answers on 443✓ answers on 443 |
| www.npmjs.com | Published2606:4700::6811:87752606:4700::6811:8675 | Answers when we connect✓ answers on 443✓ answers on 443 |
Publishedaspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.com | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6 | |
| Nameservers | Publishedbayan.ns.cloudflare.comsandy.ns.cloudflare.com | Answers when we connect✓ has IPv6✓ has IPv6 |
Lineage
Our records: Oct 18, 2013 → Nov 1, 2026Oldest registry snapshot we hold: 2014 · 6 renewals on record · DNS at Cloudflare · 3 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
What changed (latest 8 of 10)
- IPv6 first measured: published, and answering on Nov 1, 2026npmjs.com has 2 IPv6 addresses. Grade A. Measured by aaaa.bot, 2026-11-01 10:31 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- Moved to MarkMonitor, Inc between Feb 16, 2023 and Feb 24, 2023From Amazon Registrar, Inc to MarkMonitor, Inc, with 2 years added. Expiry moved from 2029-03-19 to 2031-03-19.
- Renewed +7 years between Nov 14, 2019 and Dec 5, 2019Expiry moved from 2022-03-19 to 2029-03-19, at Amazon Registrar, Inc.
- Moved to Amazon Registrar, Inc between Oct 11, 2019 and Nov 14, 2019From Oracle Corporation to Amazon Registrar, Inc, with 1 year added. Expiry moved from 2021-03-19 to 2022-03-19.
- Renewed +2 years between Feb 20, 2019 and Mar 13, 2019Expiry moved from 2019-03-19 to 2021-03-19, at Oracle Corporation.
- DNS moved to Cloudflare between Aug 29, 2018 and Aug 31, 2018ns1.p05.dynect.net, ns2.p05.dynect.net, ns3.p05.dynect.net, ns4.p05.dynect.net → bayan.ns.cloudflare.com, sandy.ns.cloudflare.com. Old set last seen in WHOIS on 2018-08-29; new set first seen in WHOIS on 2018-08-31.
- Renewed +2 years between Feb 21, 2017 and Mar 5, 2017Expiry moved from 2017-03-19 to 2019-03-19, at Oracle Corporation.
- Moved to Oracle Corporation between Feb 26, 2014 and Jul 9, 2016From Name.com, Inc to Oracle Corporation, with 2 years added. Expiry moved from 2015-03-19 to 2017-03-19.
Registrar and renewals: 328 WHOIS/RDAP snapshots, 2014-02-26 to 2026-05-19 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 106 .com zone-file snapshots held, 2013-10-18 to 2026-11-01.
Nameservers, WHOIS snapshots: 291 WHOIS/RDAP snapshots that listed nameservers, 2014-02-26 to 2026-06-21 (who.is archive). A change is placed between the nearest observations on either side, from whichever source made them; where the two sources disagree, both are shown.
Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.
Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.
Want to know when npmjs.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2010 — the same year as t.me, dnsowl.com and cdn-apple.com.