linkedin.la - robtex.com

linkedin.la

DNSSEC⚠️ Not signed
A2620:109:c002::6cae:a18πŸ‡ΊπŸ‡Έ LINKEDIN-12620:109:c002::/48 LinkedIn 2029 Stierlin Ct Mountain View, CA 94043
A108.174.10.24πŸ‡ΊπŸ‡Έ LINKEDIN-1108.174.10.0/24 Linkedin 2029 Stierlin Ct Mountain View, CA 94043 USA
NSns1-42.azure-dns.com ⭐
A150.171.10.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns1-42.azure-dns.com
NSns2-42.azure-dns.net
A150.171.16.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
PTRns2-42.azure-dns.net
NSns3-42.azure-dns.org
A13.107.222.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns3-42.azure-dns.org
NSns4-42.azure-dns.info
A13.107.206.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
PTRns4-42.azure-dns.info
TXTv=spf1 -all
TXT_rv9cqs8sj99itvm7hmwnnk345y40gxf
TXTpwc2dnmr8f1cq9wrc3zfsny9kz7bbjny
TXTrf8hg361sttmy3crckw9m0gw7db3y1wf
SOAns1-42.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

la

DNSSECπŸ”’ Signed (DS record present)
NSns0.nic.la ⭐
NSns1.nic.la
NSns2.nic.la
NSns3.nic.la
NSns4.nic.la
SOAns0.nic.lahostmaster@nic.la serial=3000733891

Same first word

Similar names

DNS History

17 records (6 active, 11 former)

20162017201820192020202120222023202420252026NSns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infons1.markmonitor.comns2.markmonitor.comns3.markmonitor.comns4.markmonitor.comns5.markmonitor.comns6.markmonitor.comns7.markmonitor.comMXbh.markmonitor.comA108.174.10.242620:109:c002::6cae:a18108.174.10.14199.101.163.1332620:109:c002::6cae:a0e
●NSns1-42.azure-dns.com2026-03-13 β†’ 2026-03-25 Β· 3 obs
β—‹ 2016-12-19 14:03:42
● 2026-03-13 18:11:00
● 2026-03-25 23:49:52
β—‹NSns1.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
●NSns2-42.azure-dns.net2026-03-13 β†’ 2026-03-25 Β· 3 obs
β—‹ 2016-12-19 14:03:42
● 2026-03-13 18:11:00
● 2026-03-25 23:49:52
β—‹NSns2.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
●NSns3-42.azure-dns.org2026-03-13 β†’ 2026-03-25 Β· 3 obs
β—‹ 2016-12-19 14:03:42
● 2026-03-13 18:11:00
● 2026-03-25 23:49:52
β—‹NSns3.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
●NSns4-42.azure-dns.info2026-03-13 β†’ 2026-03-25 Β· 3 obs
β—‹ 2016-12-19 14:03:42
● 2026-03-13 18:11:00
● 2026-03-25 23:49:52
β—‹NSns4.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
β—‹NSns5.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
β—‹NSns6.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
β—‹NSns7.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
β—‹MXbh.markmonitor.com2015-07-06 β†’ 2016-12-19 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
β—‹A108.174.10.142016-02-16 β†’ 2016-12-19 Β· 5 obs
β—‹ 2016-01-22 13:16:20
● 2016-02-16 20:36:54
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
●A108.174.10.242026-03-13 β†’ 2026-03-25 Β· 3 obs
β—‹ 2016-12-19 14:03:42
● 2026-03-13 18:11:00
● 2026-03-25 23:49:52
β—‹A199.101.163.1332015-07-06 β†’ 2016-01-22 Β· 4 obs
● 2015-07-06 17:38:58
● 2016-01-22 13:16:20
β—‹ 2016-02-16 20:36:54
β—‹ 2026-03-25 23:49:52
β—‹A2620:109:c002::6cae:a0e2016-02-16 β†’ 2016-12-19 Β· 5 obs
β—‹ 2016-01-22 13:16:20
● 2016-02-16 20:36:54
● 2016-12-19 14:03:42
β—‹ 2026-03-13 18:11:00
β—‹ 2026-03-25 23:49:52
●A2620:109:c002::6cae:a182026-03-13 β†’ 2026-03-25 Β· 3 obs
β—‹ 2016-12-19 14:03:42
● 2026-03-13 18:11:00
● 2026-03-25 23:49:52

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
lans1.nic.la, ns2.nic.la, ns3.nic.la, ns4.nic.la-
linkedin.lans1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info-

βœ… Authoritative Response

Server:13.107.206.42

NS records: ns1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedin.la (unsigned zone)

⏱️ Timing

Total: 165ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1108.174.10.24
AAAA12620:109:c002::6cae:a18
NS4ns1-42.azure-dns.com, ns2-42.azure-dns.net...
MX1. (pri: 0)
TXT4_rv9cqs8sj99itvm7hmwnnk345y40gxf, pwc2dnmr8f1cq9wrc3zfsny9kz7bbjny...
SOA1ns1-42.azure-dns.com azuredns-hostmaster

Analysis

IP Addresses

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

Other host names such as newsle.net, linkedinbabes.com, linkedinbot.com, linkedinsoftware.tools and hrtech.co share IPs with linkedin.la.

Name Servers

linkedin.la is delegated to four name servers: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.

linkedin.la at least partially shares name servers with other domains, for instance linkedinprofile.directory, linkedintools-ei.com, newsly.com, linkedin.ca and lnkdns.net.

These name servers are commonly used alongside dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, 1.ns.linkedin.com, 2.ns.linkedin.com, 3.ns.linkedin.com, 4.ns.linkedin.com, 5.ns.linkedin.com and 6.ns.linkedin.com.

Host names with one IP number:

ns1-42.azure-dns.com points to 150.171.10.42.

ns4-42.azure-dns.info points to 13.107.206.42.

ns2-42.azure-dns.net points to 150.171.16.42.

ns3-42.azure-dns.org points to 13.107.222.42.