Check-Host.cc

Domain

sg.linkedin.com

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

Run a live full scan of sg.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
20
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
13
in our scans

DNS Records

A
104.18.41.41, 150.171.109.100, 150.171.109.101, 150.171.109.33, 150.171.109.34, 150.171.109.36, 150.171.110.53, 172.64.146.215
AAAA
2603:1061:14:133::1, 2603:1061:14:174::1, 2603:1061:14:20::1, 2603:1061:14:21::1, 2603:1061:14:23::1, 2603:1061:14:63::1, 2603:1061:14:64::1, 2603:1061:14:c4::1
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

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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.

Threat Intelligence

Domain threat-intel pending

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

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
AAAA 2603:1061:14:21::1 2026-05-25 22:07:29.493 2026-05-26 23:18:43.916
A 150.171.109.36 2026-05-25 22:07:29.493 2026-05-26 23:18:43.916
AAAA 2603:1061:14:64::1 2026-05-26 02:59:13.593 2026-05-27 15:52:01.622
A 150.171.109.34 2026-05-26 02:59:13.593 2026-05-27 10:34:14.234
A 150.171.109.33 2026-05-26 03:07:47.855 2026-05-26 23:04:58.757
AAAA 2603:1061:14:20::1 2026-05-26 03:07:47.855 2026-05-26 23:04:58.757
A 150.171.109.101 2026-05-26 04:11:07.627 2026-05-27 15:52:01.622
AAAA 2603:1061:14:133::1 2026-05-26 04:56:37.608 2026-05-26 04:56:37.608
AAAA 2603:1061:14:63::1 2026-05-26 13:52:57.285 2026-05-27 14:49:12.821
A 150.171.109.100 2026-05-26 13:52:57.285 2026-05-27 07:21:42.379
AAAA 2603:1061:14:174::1 2026-05-26 19:52:55.674 2026-05-26 21:57:05.653
AAAA 2603:1061:14:23::1 2026-05-26 23:14:12.044 2026-05-26 23:14:12.044
AAAA 2a06:98c1:3102::6812:2929 2026-06-14 22:52:09.672 2026-06-22 18:12:13.529
A 104.18.41.41 2026-06-14 22:52:09.672 2026-07-28 05:49:37.765
A 172.64.146.215 2026-06-14 22:52:09.672 2026-07-28 05:49:37.765
AAAA 2606:4700:4407::ac40:92d7 2026-06-14 22:52:09.672 2026-06-22 18:12:13.529
AAAA 2603:1061:14:c4::1 2026-06-19 00:33:54.212 2026-06-19 00:33:54.212
A 150.171.110.53 2026-06-19 00:33:54.212 2026-06-19 00:33:54.212
AAAA 2a06:98c1:3109::6812:2929 2026-07-16 15:56:33.652 2026-07-28 05:49:37.765
AAAA 2a06:98c1:310b::ac40:92d7 2026-07-16 15:56:33.652 2026-07-28 05:49:37.765