`rum2.perf.linkedin.com`

	CNAME	`ln-0004.ln-msedge.net`
	DNSSEC	⚠️ Not signed
	A	2620:1ec:50::14^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
	A	150.171.22.14^{🇺🇸 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

2mur.ru

umr2.com

mur2.net

mur2.info

rm2u.net

DNS History

14 records (1 active, 13 former)

○A108.174.10.102016-12-12 → 2016-12-12 · 4 obs

○ 2016-12-07 17:14:48
● 2016-12-12 20:38:16
○ 2017-01-23 18:44:32
○ 2026-05-10 16:02:16

○A185.63.144.12017-01-23 → 2017-01-23 · 4 obs

○ 2016-12-12 20:38:16
● 2017-01-23 18:44:32
○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

○A2620:109:c002::6cae:a0a2016-12-12 → 2016-12-12 · 4 obs

○ 2016-12-07 17:14:48
● 2016-12-12 20:38:16
○ 2017-01-23 18:44:32
○ 2026-05-10 16:02:16

○A2620:109:c007:102::5be1:f8812016-12-07 → 2016-12-07 · 3 obs

● 2016-12-07 17:14:48
○ 2016-12-12 20:38:16
○ 2026-05-10 16:02:16

○A2620:109:c00c:104::b93f:90012017-01-23 → 2017-01-23 · 4 obs

○ 2016-12-12 20:38:16
● 2017-01-23 18:44:32
○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

○A91.225.248.1292016-12-07 → 2016-12-07 · 3 obs

● 2016-12-07 17:14:48
○ 2016-12-12 20:38:16
○ 2026-05-10 16:02:16

○CNAMEany-na.www.linkedin.com2016-12-12 → 2016-12-12 · 4 obs

○ 2016-12-07 17:14:48
● 2016-12-12 20:38:16
○ 2017-01-23 18:44:32
○ 2026-05-10 16:02:16

○CNAMEglb-any-eu.www.linkedin.com2016-12-07 → 2017-01-23 · 5 obs

● 2016-12-07 17:14:48
○ 2016-12-12 20:38:16
● 2017-01-23 18:44:32
○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

○CNAMEglb-eu.www.linkedin.com2016-12-07 → 2017-01-23 · 5 obs

● 2016-12-07 17:14:48
○ 2016-12-12 20:38:16
● 2017-01-23 18:44:32
○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

○CNAMEl-0007.l-msedge.net2026-05-01 → 2026-05-10 · 2 obs

○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

●CNAMEln-0004.ln-msedge.net2026-05-01 → 2026-05-10 · 3 obs

○ 2017-01-23 18:44:32
● 2026-05-01 22:53:08
● 2026-05-10 16:02:16

○CNAMEpop-idb2-alpha.www.linkedin.com2016-12-07 → 2016-12-07 · 3 obs

● 2016-12-07 17:14:48
○ 2016-12-12 20:38:16
○ 2026-05-10 16:02:16

○CNAMEpop-tln1-alpha.www.linkedin.com2017-01-23 → 2017-01-23 · 4 obs

○ 2016-12-12 20:38:16
● 2017-01-23 18:44:32
○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

○CNAMEwww.linkedin.com2016-12-07 → 2017-01-23 · 4 obs

● 2016-12-07 17:14:48
● 2017-01-23 18:44:32
○ 2026-05-01 22:53:08
○ 2026-05-10 16:02:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net, a.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: 286ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 1

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

Analysis

IP Addresses

rum2.perf.linkedin.com resolves to two IP numbers: 2620:1ec:50::14 and 150.171.22.14.

Other host names, for instance, ipv4.ln-0004.ln-msedge.net and ln-0004.ln-msedge.net share IP numbers with rum2.perf.linkedin.com.

rum2.perf.linkedin.com - robtex.com