`rum11.perf.linkedin.com`

	CNAME	`ln-0002.ln-msedge.net`
	DNSSEC	⚠️ Not signed
	A	2620:1ec:50::12^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
	A	150.171.22.12^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}

`perf.linkedin.com`

DNSSEC

⚠️ Not signed

⚠️ On DNS blocklist: pro.plus, ultimate
WOT: SAFE (64/100)
WOT: SAFE (78/100)

Similar names

11rum.com

DNS History

3 records (1 active, 2 former)

○CNAMEl-0005.l-msedge.net2026-03-08 → 2026-03-08 · 3 obs

○ 2017-09-22 07:11:32
● 2026-03-08 22:04:44
○ 2026-05-11 17:42:56

○CNAMElinkedin-esg3.teridions.net2017-09-22 → 2017-09-22 · 3 obs

● 2017-09-22 07:11:32
○ 2026-03-08 22:04:44
○ 2026-05-11 17:42:56

●CNAMEln-0002.ln-msedge.net2026-05-11 → 2026-05-11 · 2 obs

○ 2026-03-08 22:04:44
● 2026-05-11 17:42:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
linkedin.com	dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net...	1 record

✅ Authoritative Response

Server:150.171.16.42

NS records: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedin.com (unsigned zone)

⏱️ Timing

Total: 270ms | Queries: -

📄 Records

Type	Count	Sample Data
CNAME	1	`ln-0002.ln-msedge.net`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns1-42.azure-dns.com)

Analysis

IP Addresses

rum11.perf.linkedin.com points to two IP numbers: 2620:1ec:50::12 and 150.171.22.12.

Other host names such as linkedin.com, lnkd.in and ln-0002.ln-msedge.net share IP numbers with rum11.perf.linkedin.com.

rum11.perf.linkedin.com - robtex.com