Check-Host.cc

Domain

content.linkedin.com

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of content.linkedin.com

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
8
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
8
in our scans

DNS Records

A
2.21.20.141, 2.21.20.155, 23.72.252.57, 23.72.252.82
AAAA
2a02:26f0:480:15::213:7e4a, 2a02:26f0:480:15::213:7e63, 2a02:26f0:b200::5435:af31, 2a02:26f0:b200::5435:af90
MX
NS
TXT
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

185.58.74.197:80 href · ×1
149.130.223.91:80 href · ×1

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

a3bd597801657c96… google · xenon2026h2
Subject: platform.linkedin.com
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
SANs: platform.linkedin.com, platform.linkedin-ei.com, platform-akam.linkedin.com, platform-akam.linkedin-ei.com, content.linkedin.com
Valid: 2026-03-20 00:00:00 → 2026-09-20 23:59:59
d4c1bcda8b3049cf… google · xenon2026h2
Subject: platform.linkedin.com
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
SANs: platform.linkedin.com, platform.linkedin-ei.com, platform-akam.linkedin.com, platform-akam.linkedin-ei.com, content.linkedin.com
Valid: 2026-03-20 00:00:00 → 2026-09-20 23:59:59
948edcb1782194fa… google · xenon2026h2
Subject: platform.linkedin.com
Issuer: DigiCert SHA2 Secure Server CA
SANs: platform.linkedin.com, platform.linkedin-ei.com, platform-akam.linkedin.com, platform-akam.linkedin-ei.com, content.linkedin.com
Valid: 2026-01-27 00:00:00 → 2026-07-27 23:59:59

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.