Linkedin.com Domain Trust Report
linkedin.com shows moderate health — SSL Certificate and Domain Expiry and Email Auth and Security Headers need attention. Review the breakdown below.
Registration & ownership
| Registrar | MarkMonitor Inc. |
| Registered | Nov 2, 2002 |
| Updated | Oct 1, 2025 |
| Expires | Nov 2, 2026 42d |
| Status | client delete prohibit.server delete prohibit. |
DNS records
| A | 130.211.32.14 |
| AAAA | 2600:1901:0:d5ad:: |
| MX | mail-c.linkedin.com (pri 10)mail-d.linkedin.com (pri 10)mail.linkedin.com (pri 20)mail-a.linkedin.com (pri 10) |
| NS | dns1.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 |
| TXT | 448e0dc03e935ecf66d81f1ce3c26b2f2fea13756c031ffc4be91749107f3a79AFDVALIDATION=LinkedIn_cthqqp5zj8g86qf3h97heqitg2zc32bapple-domain-verification=Hp7LihDNsREwfHX9atlassian-domain-verification=dDed2VFvlDajBX8X22w52Jx/W/YLHR81SxUuraa9zNdz4aLjDS… +19 more |
Hosting & network
| IP address | 130.211.32.14 |
| IPv6 | 2600:1901:0:d5ad:: |
| Nameservers | dns1.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 |
| Protocol | HTTPS HTTP/2 |
| IPv6 support | ENABLED |
SSL / TLS
Technology detected
30-day availability
Email authentication
Monitoring events
What we know about Linkedin.com
Linkedin.com has been registered for 23 years (since Nov 2, 2002), managed through MarkMonitor Inc., ranked #19 globally by Tranco, categorised as professional network. Its current health score is 72/100 (grade C) — generally healthy but with some configuration gaps worth reviewing. As a professional network handling career and business identity data, its TLS configuration, DMARC enforcement, and security headers are essential trust anchors.
linkedin.com's security posture: SSL certificate needs attention — only 60 days until expiry; security headers have gaps; no blacklist entries found.
SPF is configured, restricting which servers can send email as this domain. DMARC policy is set to "reject" — spoofed emails are rejected.
linkedin.com resolves to 130.211.32.14, IPv6 is enabled, DNS is managed through dns1.p09.nsone.net and dns2.p09.nsone.net (+6 more), email routed through 4 MX records.
This snapshot is from 29m ago. Run it live in one click.
Get a fresh scan of linkedin.com across all 25 tools — or scan any domain you own. Free, no card.
Do more with DomainScan
Everything you need to secure, monitor, and understand any domain — including linkedin.com.
Continuous monitoring for linkedin.com
Detect DNS drift, SSL expiry, DMARC changes, WHOIS transfers, and blacklist hits automatically — 24/7 with severity-classified alerts.
Explore the PlatformEmbed a live Trust Badge
Show visitors your domain passes 14 safety checks. Live-verified SVG re-scores on every fetch — no stale seals, no maintenance.
Get a Trust Badge50+ tools, one JSON API
Automate WHOIS, DNS, SSL, blacklist, DMARC, headers, and typosquat checks in your app. Predictable schema, generous free tier.
Read API docsMCP for AI agents
Give ChatGPT, Claude, Cursor, and any Model Context Protocol client direct access to every DomainScan tool. Zero glue code.
Set up MCPAsk Prism about linkedin.com
Chat with our AI domain analyst. Get plain-English answers on DNS posture, email auth, blacklist state, and reputation risk.
Open Prism AIHow DNS, SSL, DMARC actually work
Free deep-dives on domain security — RDAP, DNSSEC, EPP status codes, phishing detection, SPF alignment, DKIM key rotation.
Visit the Learning Hub