`rum14.perf.linkedin.com`

	CNAME	`www-linkedin-com.ln-0002.ln-msedge.net`
	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)

DNS History

2 records (1 active, 1 former)

○CNAMEl-0005.l-msedge.net2018-05-15 → 2018-05-15 · 3 obs

● 2018-05-15 02:30:32
○ 2026-02-15 11:10:52
○ 2026-05-10 23:16:30

●CNAMEwww-linkedin-com.ln-0002.ln-msedge.net2026-02-15 → 2026-05-10 · 3 obs

○ 2018-05-15 02:30:32
● 2026-02-15 11:10:52
● 2026-05-10 23:16:30

🔍 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:198.51.45.73

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: 280ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 1

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

Analysis

IP Addresses

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

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

rum14.perf.linkedin.com - robtex.com