CF1757958080526-tsm20250915173524

IPLIST.NET - linkedin.no

Search for IP or hostnames:

linkedin.no checked at 2025-09-15T17:41:20.478Z 488ms 73/73/73 100% R:17

linkedin.no

MX.
NSns1-42.azure-dns.com
A150.171.10.42🇺🇸 Microsoft
PTRns1-42.azure-dns.com
NSns4-42.azure-dns.info
A13.107.206.42🇺🇸 Microsoft
PTRns4-42.azure-dns.info
NSns2-42.azure-dns.net
A150.171.16.42🇺🇸 Microsoft
PTRns2-42.azure-dns.net
NSns3-42.azure-dns.org
A13.107.222.42🇺🇸 Microsoft
PTRns3-42.azure-dns.org
A2620:109:c002::6cae:a18 🇺🇸 LinkedIn
A108.174.10.24🇺🇸 LinkedIn
PTR108-174-10-24.fwd.linkedin.com

no

NSi.nic.no
NSx.nic.no
NSy.nic.no
NSz.nic.no
NSnjet.norid.no
NSnot.norid.no

Starts with same word

Starts similarily

AI analysis

linkedin.no points to two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.

IP numbers are shared between linkedin.no and other host names such as lynda.co, 108-174-10-24.fwd.linkedin.com, linkedinprofile.directory, newsly.com, and linkedin.ca.

Four name servers, ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net, and ns3-42.azure-dns.org, are delegated to linkedin.no.

Name servers of linkedin.no are at least partially shared with other domains such as newsle.co, linkedin.biz, linkedin.directory, linkedin.com.tr, and linkedindirectory.com.

The name servers dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, and dns4.p09.nsone.net are frequently used in conjunction.

ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net, and ns3-42.azure-dns.org all point to different IP numbers: 150.171.10.42, 13.107.206.42, 150.171.16.42, and 13.107.222.42 respectively.

The mail server, ., handles linkedin.no.

The mail server setup of linkedin.no is identical to that of other domains such as veindia.com, ns.brim.info, www.keps.com, tuscanhill.com, and truefitness.us.

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

DRXlwMQ CF johedugfp 2025-09-15