rum9.perf.linkedin.com - robtex.com

rum9.perf.linkedin.com

CNAMElinkedin.map.fastly.net
DNSSEC⚠️ Not signed
A2a04:4e42:56::810πŸ‡ΊπŸ‡Έ Fastly2a04:4e42:56::/48
A199.232.39.42πŸ‡ΊπŸ‡Έ Fastly199.232.36.0/22

perf.linkedin.com

DNSSEC⚠️ Not signed
WOT: SAFE (64/100)
WOT: SAFE (78/100)

Same first word

Similar names

DNS History

5 records (1 active, 4 former)

2017201820192020202120222023202420252026A108.174.13.102620:109:c001::6cae:d0aCNAMElinkedin.map.fastly.net2-01-2c3e-005a.cdx.cedexis.netac.perf.linkedin.com
β—‹A108.174.13.102016-12-27 β†’ 2016-12-27 Β· 3 obs
● 2016-12-27 19:07:58
β—‹ 2019-09-05 02:05:58
β—‹ 2026-05-11 04:15:14
β—‹A2620:109:c001::6cae:d0a2016-12-27 β†’ 2016-12-27 Β· 3 obs
● 2016-12-27 19:07:58
β—‹ 2019-09-05 02:05:58
β—‹ 2026-05-11 04:15:14
β—‹CNAME2-01-2c3e-005a.cdx.cedexis.net2019-09-05 β†’ 2019-10-17 Β· 5 obs
β—‹ 2016-12-27 19:07:58
● 2019-09-05 02:05:58
● 2019-10-17 19:41:48
β—‹ 2026-03-08 21:56:16
β—‹ 2026-05-11 04:15:14
β—‹CNAMEac.perf.linkedin.com2016-12-27 β†’ 2016-12-27 Β· 3 obs
● 2016-12-27 19:07:58
β—‹ 2019-09-05 02:05:58
β—‹ 2026-05-11 04:15:14
●CNAMElinkedin.map.fastly.net2026-03-08 β†’ 2026-05-11 Β· 3 obs
β—‹ 2019-10-17 19:41:48
● 2026-03-08 21:56:16
● 2026-05-11 04:15:14

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
linkedin.comdns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net...-

βœ… 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: 64ms | Queries: -

πŸ“„ Records

TypeCountSample Data
CNAME1linkedin.map.fastly.net

Analysis

IP Addresses

rum9.perf.linkedin.com points to two IPs: 2a04:4e42:56::810 and 199.232.39.42.

Other host names, for example, linkedin.map.fastly.net share IP numbers with rum9.perf.linkedin.com.