Domain Intelligence Report

lnkd.in

Compare

IPv6

Measured 2026-11-01 04:02 UTC · aaaa.bot
A

Website, 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.

lnkd.inPublished2600:1901:0:d5ad::Answers when we connect✓ answers on 443
MailPublishedmail-2.linkedin.commail-3.linkedin.comAnswers when we connect✓ has IPv6✓ has IPv6
NameserversPublisheddns1.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.infoAnswers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✗ no IPv6✗ no IPv6✗ no IPv6✗ no IPv6
First measured with IPv6 on 2026-11-01Changes are recorded from here on, each with its date.

Lineage

Our records: Apr 15, 2010 → Nov 1, 2026

Oldest registry snapshot we hold: 2010 · 6 renewals on record. These dates are when our records begin, not when the domain was registered.

Registrar
120 snapshots
Mark Monitor (R84-AFIN)Renewed +2 yearsbetween Feb 8, 2012 and Apr 9, 2012Expiry moved from 2012-04-09 to 2014-04-09, at Mark Monitor (R84-AFIN).Renewed +2 yearsbetween Mar 2, 2014 and Mar 22, 2014Expiry moved from 2014-04-09 to 2016-04-09, at Mark Monitor (R84-AFIN).Renewed +2 yearsbetween Jan 23, 2016 and Mar 15, 2016Expiry moved from 2016-04-09 to 2018-04-09, at Mark Monitor (R84-AFIN).Renewed +2 yearsbetween Nov 18, 2017 and Apr 11, 2018Expiry moved from 2018-04-09 to 2020-04-09, at MarkMonitor Inc. (R84-AFIN).Renewed +6 yearsbetween Apr 27, 2018 and May 2, 2025Expiry moved from 2020-04-09 to 2026-04-09, at MarkMonitor Inc.Renewed +1 yearbetween Feb 7, 2026 and May 4, 2026Expiry moved from 2026-04-09 to 2027-04-09, at MarkMonitor Inc.
Nameservers
seen in WHOIS
Oracle Dyn + linkedin.comDNS moved to Oracle Dyn + UltraDNS (Neustar/Vercara) + ultradns.co.ukbetween Jul 1, 2012 and Dec 17, 2012pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk → ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net, pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk. Old set last seen in WHOIS on 2012-07-01; new set first seen in WHOIS on 2012-12-17.DNS moved to Oracle Dyn + linkedin.combetween Jan 5, 2013 and Feb 28, 2013ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net, pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk → ns1.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, ns5.linkedin.com, ns6.linkedin.com. Old set last seen in WHOIS on 2013-01-05; new set first seen in WHOIS on 2013-02-28.DNS moved to NS1 + Oracle Dynbetween 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.DNS moved to Microsoft Azure DNS + NS1between 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.
IPv6
aaaa.bot check
2014201820222026
What changed (latest 8 of 11)
  1. 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.
  2. Renewed +1 year between Feb 7, 2026 and May 4, 2026Expiry moved from 2026-04-09 to 2027-04-09, at MarkMonitor Inc.
  3. 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.
  4. Renewed +6 years between Apr 27, 2018 and May 2, 2025Expiry moved from 2020-04-09 to 2026-04-09, at MarkMonitor Inc.
  5. 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).
  6. 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.
  7. 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).
  8. 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.

Gathering intelligence... (12/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Outline
WHOIS
MarkMonitor Inc. · registered 17 years ago · expires Apr 9, 2027
DNS
1 A · 3 MX · 8 NS · 1 CAA · 1 PTR · 1 SOA · 8 TXT · 1 AAAA
SSL/TLS
DigiCert Inc · TLSv1.3 · expires in 139d · 39 SANs
Email Auth
SPF ✓ · DKIM ✗ · DMARC ✓ (p=reject)
DNSSEC
not signed
Tech Stack
Host: Google LLC · Email: Self-hosted · DNS: Azure DNS · Cloudflare
HTTP
1 redirect → 200 · HSTS ✓ · CSP ✓ · X-Frame ✓ · Nosniff ✓
Security
B (175/215) · 1 critical · 1 high
Threats
risk: medium
Deliverability
A+ (90/90) · 3 MX · 7 IPs · 1 issue(s)
Subdomains
0 found · 104 answered (8 timed out)
Web Archive
DNS Recordschecked 25.6d ago
Details
1 A · 3 MX · 8 NS · 1 CAA · 1 PTR · 1 SOA · 8 TXT · 1 AAAA
WHOISchecked 25.6d ago
Details
MarkMonitor Inc.
Registered 17 years ago
Expires Apr 9, 2027
Then vs Nownew
No card for this name. We compare then and now for domains that are in the top million and had an AboutUs page. That says nothing about this domain’s age or safety.
Check what it is now →
SSL/TLSchecked 25.6d ago
Details
Valid certificate
Issuer: DigiCert Inc
Protocol: TLSv1.3
Expires in 139 days
39 SAN(s)
Securitychecked 25.6d ago
Details
B
175/215
1 critical1 high
Weakest: Basic Security, Record Security
Email Authchecked 25.6d ago
Details
SPFDKIM?DMARC
Policy: reject
DNSSECchecked 25.6d ago
Details
Not DNSSEC-signed
Tech Stackchecked 25.6d ago
Details
Google LLCCloudflareEmail: Self-hostedDNS: Azure DNS
HTTP / Headerschecked 25.6d ago
Details
1 redirect(s) → 200
HSTSCSPX-FrameNosniff
Threatschecked 25.6d ago
Details
Risk: medium · score 0.6999999999999998
Zone census
Subdomainschecked 25.6d ago
Details
0 found · 104 answered · 8 timed out (unknown)
Click a subdomain for its full report
Web Archivechecked 25.6d ago
Details
First archived: unknown
Deliverabilitychecked 25.6d ago
Details
A+
90/90 · 1 issue(s)
3 MX · 7 IP(s)

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.

Monitor lnkd.in

Explore related

Registered in 2009 — the same year as cloudflare.com, whatsapp.net and pinterest.com.