`rum6.perf.linkedin.com`

	CNAME	`gcp-lb.www.linkedin.com`
	DNSSEC	⚠️ Not signed
	A	2600:1901:0:d5ad::^{🇺🇸 Google2600:1901::/32}
	A	130.211.32.14^{🇺🇸 Google130.211.0.0/17}

`perf.linkedin.com`

DNSSEC

⚠️ Not signed

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

Similar names

urm6.mobi

DNS History

5 records (1 active, 4 former)

○A185.63.147.102016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 06:41:40
○ 2021-11-11 07:07:48
○ 2026-05-11 04:15:00

○CNAME2-01-2c3e-0045.cdx.cedexis.net2021-11-11 → 2021-11-11 · 4 obs

○ 2016-12-21 06:41:40
● 2021-11-11 07:07:48
○ 2026-05-11 04:14:58
○ 2026-05-11 04:15:00

○CNAMEacpc.perf.linkedin.com2016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 06:41:40
○ 2021-11-11 07:07:48
○ 2026-05-11 04:15:00

○CNAMEedge-poc-gcp.perf.linkedin.com2026-05-11 → 2026-05-11 · 2 obs

○ 2026-05-11 04:14:58
○ 2026-05-11 04:15:00

●CNAMEgcp-lb.www.linkedin.com2026-05-11 → 2026-05-11 · 3 obs

○ 2021-11-11 07:07:48
● 2026-05-11 04:14:58
● 2026-05-11 04:15:00

🔍 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.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: 353ms | Queries: -

📄 Records

Type	Count	Sample Data
CNAME	1	`gcp-lb.www.linkedin.com`

📌 Glue Records Collected

Total: 1

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

Analysis

IP Addresses

The entity rum6.perf.linkedin.com points to two IP numbers: 2600:1901:0:d5ad:: and 130.211.32.14.

Other host names, for instance, gcp-lb.www.linkedin.com share IP numbers with rum6.perf.linkedin.com.

rum6.perf.linkedin.com - robtex.com