lnkd.in
IPv6
Measured 2026-11-01 04:02 UTC · aaaa.botWebsite, mail and DNS all work over IPv6.
The published IPv6 address accepted a connection when we tried it.
- ✓ lnkd.in answers (1 of 1 addresses)
- ✓ Mail: 2 of 2 servers have IPv6
- ✓ Nameservers: 4 of 8 have IPv6
Details: published addresses and what answered
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| lnkd.in | Published2600:1901:0:d5ad:: | Answers when we connect✓ answers on 443 |
Publishedmail-2.linkedin.commail-3.linkedin.com | Answers when we connect✓ has IPv6✓ has IPv6 | |
| Nameservers | Publisheddns1.p09.nsone.netdns2.p09.nsone.netdns3.p09.nsone.netdns4.p09.nsone.netns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.info | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✗ no IPv6✗ no IPv6✗ no IPv6✗ no IPv6 |
Lineage
Our records: Apr 15, 2010 → Nov 1, 2026Oldest registry snapshot we hold: 2010 · 6 renewals on record. These dates are when our records begin, not when the domain was registered.
What changed (latest 8 of 11)
- IPv6 first measured: published, and answering on Nov 1, 2026lnkd.in has 1 IPv6 address. Grade A. Measured by aaaa.bot, 2026-11-01 04:02 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- Renewed +1 year between Feb 7, 2026 and May 4, 2026Expiry moved from 2026-04-09 to 2027-04-09, at MarkMonitor Inc.
- DNS moved to Microsoft Azure DNS + NS1 between Apr 27, 2018 and May 2, 2025dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net → dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info. Old set last seen in WHOIS on 2018-04-27; new set first seen in WHOIS on 2025-05-02.
- Renewed +6 years between Apr 27, 2018 and May 2, 2025Expiry moved from 2020-04-09 to 2026-04-09, at MarkMonitor Inc.
- Renewed +2 years between Nov 18, 2017 and Apr 11, 2018Expiry moved from 2018-04-09 to 2020-04-09, at MarkMonitor Inc. (R84-AFIN).
- DNS moved to NS1 + Oracle Dyn between Oct 3, 2016 and Oct 30, 2016ns1.linkedin.com, ns1.p43.dynect.net, ns2.linkedin.com, ns2.p43.dynect.net, ns3.linkedin.com, ns3.p43.dynect.net, ns4.linkedin.com, ns4.p43.dynect.net → dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net. Old set last seen in WHOIS on 2016-10-03; new set first seen in WHOIS on 2016-10-30.
- Renewed +2 years between Jan 23, 2016 and Mar 15, 2016Expiry moved from 2016-04-09 to 2018-04-09, at Mark Monitor (R84-AFIN).
- Renewed +2 years between Mar 2, 2014 and Mar 22, 2014Expiry moved from 2014-04-09 to 2016-04-09, at Mark Monitor (R84-AFIN).
Registrar and renewals: 120 WHOIS/RDAP snapshots, 2010-04-15 to 2026-05-04 (ledger built 2026-09-27). Every renewal
Nameservers, WHOIS snapshots: 116 WHOIS/RDAP snapshots that listed nameservers, 2010-04-15 to 2026-05-04 (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 lnkd.in changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2009 — the same year as cloudflare.com, whatsapp.net and pinterest.com.