HOW.IS
?

How is lnkd.in?

Looks fine risk 0/100

Registered 18 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 289 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How lnkd.in looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
289 ms · ends at www.linkedin.com
HTTPS
113 d
left on a DigiCert Inc certificate
Age
18 years
registered 2009-04-09
Blocklists
0
listings across 4 lists; 1 did not answer

Everything we looked at

DNS records6 record types
A130.211.32.14
AAAA2600:1901:0:d5ad::
MX10 mail-3.linkedin.com
10 mail-2.linkedin.com
NSdns4.p09.nsone.net
dns3.p09.nsone.net
ns3-42.azure-dns.org
ns1-42.azure-dns.com
dns2.p09.nsone.net
ns4-42.azure-dns.info
dns1.p09.nsone.net
ns2-42.azure-dns.net
TXTAFDVALIDATION=LinkedIn
_wwbw1h78de5e0kgs9cq26eurbu67yov
_5z562799n5du0lh7df5w00s6cviuy4a
CM-94033
56knd6gkhl82315qt77qgvmtwb149hhz
v=spf1 -all
1rnz0xkbmgwm1km8jg4802414n8ffv6q
_qudegu7ve2p7h2g31ajv487ixwhf0vd
CAA{'type': 'CAA', 'critical': 0, 'contactemail': 'caarecordaware@microsoft.com'}
RegistrationMarkMonitor Inc.
registrarMarkMonitor Inc.
registered2009-04-09
expires2027-04-09
last changed2026-03-13
ownerLinkedIn Corporation
nameserversns1-42.azure-dns.com
dns1.p09.nsone.net
ns4-42.azure-dns.info
dns2.p09.nsone.net
dns3.p09.nsone.net
ns2-42.azure-dns.net
ns3-42.azure-dns.org
dns4.p09.nsone.net
statusclient update prohibited
client transfer prohibited
client delete prohibited
registered 2009-04-09expires 2027-04-09
HTTPS certificate113 days left
validyes
issuerDigiCert Inc
coverswww.linkedin.com, linkedin.com, rum5.perf.linkedin.com, exp4.www.linkedin.com, exp3.www.linkedin.com, exp2.www.linkedin.com, exp1.www.linkedin.com, rum2.perf.linkedin.com, rum4.perf.linkedin.com, rum6.perf.linkedin.com, rum17.perf.linkedin.com, rum8.perf.linkedin.com
protocolTLSv1.3
issued 2026-08-22expires 2027-02-22
DNSSECinsecure

Domain is not signed with DNSSEC

. → in → lnkd.in
Email authenticationgood
SPFpass v=spf1 -all
DMARCpass policy reject
DKIMnone of 1 common selectors

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade A · 180/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
45/45missing: DKIM Presence
Advanced Security
20/25missing: SOA Record Configuration
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop130.211.32.14Barracuda130.211.32.14UCEPROTECT Level 1130.211.32.14

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.

curl "https://how.is/v1/domain/trust?domain=lnkd.in" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=lnkd.in"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on lnkd.in. Reference: /llms.txt.

IPv6. IPv6 readiness grade for lnkd.in Does lnkd.in work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

Watch lnkd.in. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.

Watch — $1 / 30 days