`rum10.perf.linkedin.com`

	CNAME	`pop-az-sh.www.linkedin.com`
	CNAME	`pop-az-sh-lor1.www.linkedin.com`
	DNSSEC	⚠️ Not signed
	A	52.130.75.155^{🇨🇳 BLUECLOUD52.130.64.0/19 Microsoft China}

`perf.linkedin.com`

DNSSEC

⚠️ Not signed

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

Subdomains

afdverify.rum10.perf.linkedin.com

DNS History

4 records (1 active, 3 former)

○A108.174.13.102016-12-09 → 2016-12-09 · 3 obs

● 2016-12-09 08:41:12
○ 2026-05-05 00:46:26
○ 2026-05-10 16:19:40

○A2620:109:c001::6cae:d0a2016-12-09 → 2016-12-09 · 3 obs

● 2016-12-09 08:41:12
○ 2026-05-05 00:46:26
○ 2026-05-10 16:19:40

○CNAMEac.perf.linkedin.com2016-12-09 → 2016-12-09 · 3 obs

● 2016-12-09 08:41:12
○ 2026-05-05 00:46:26
○ 2026-05-10 16:19:40

●CNAMEpop-az-sh.www.linkedin.com2026-05-05 → 2026-05-10 · 3 obs

○ 2016-12-09 08:41:12
● 2026-05-05 00:46:26
● 2026-05-10 16:19:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.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.10.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: 341ms | Queries: -

📄 Records

Type	Count	Sample Data
CNAME	1	`pop-az-sh.www.linkedin.com`

📌 Glue Records Collected

Total: 1

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

Analysis

Hierarchy

The parent of afdverify.rum10.perf.linkedin.com is rum10.perf.linkedin.com.

IP Addresses

rum10.perf.linkedin.com points to IP number: 52.130.75.155.

Other host names, for instance pop-az-sh-lor1.www.linkedin.com share IP numbers with rum10.perf.linkedin.com.

rum10.perf.linkedin.com - robtex.com