linked.in - robtex.com

linked.in

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
TXTh9(0x733378)14lzb7zmz60cjt5mx98w8010cfd
TXTtjl26r6qmn0jfkjjjg2zp4xbby4ln6gr
TXTv=spf1 -all
SOAns1-42.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

in

DNSSECπŸ”’ Signed (DS record present)
NSns01.trs-dns.com ⭐
NSns.trs-dns.com
NSns01.trs-dns.net
NSns10.trs-dns.info
NSns10.trs-dns.org
SOAns.trs-dns.comtrs-ops@tucows.com serial=1771291558
rank #313573 globally
rank #2014 in the tld
WOT: UNKNOWN (79/100)
πŸ“ˆ Tranco rank: #554,834

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.comMXA108.174.10.242620:109:c002::6cae:a18108.174.10.142620:109:c002::6cae:a0e72.52.10.14
●NSns1-42.azure-dns.com2026-03-01 β†’ 2026-03-01 Β· 3 obs
β—‹ 2021-11-06 09:13:26
● 2026-03-01 00:23:22
● 2026-03-01 03:46:24
β—‹NSns1.markmonitor.com2015-06-20 β†’ 2017-01-22 Β· 4 obs
● 2015-06-20 12:31:00
● 2017-01-22 13:11:40
β—‹ 2021-11-06 09:13:26
β—‹ 2026-03-01 03:46:24
●NSns2-42.azure-dns.net2026-03-01 β†’ 2026-03-01 Β· 3 obs
β—‹ 2021-11-06 09:13:26
● 2026-03-01 00:23:22
● 2026-03-01 03:46:24
β—‹NSns2.markmonitor.com2015-06-20 β†’ 2021-11-06 Β· 4 obs
● 2015-06-20 12:31:00
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
●NSns3-42.azure-dns.org2026-03-01 β†’ 2026-03-01 Β· 3 obs
β—‹ 2021-11-06 09:13:26
● 2026-03-01 00:23:22
● 2026-03-01 03:46:24
β—‹NSns3.markmonitor.com2015-06-20 β†’ 2021-11-06 Β· 4 obs
● 2015-06-20 12:31:00
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
●NSns4-42.azure-dns.info2026-03-01 β†’ 2026-03-01 Β· 3 obs
β—‹ 2021-11-06 09:13:26
● 2026-03-01 00:23:22
● 2026-03-01 03:46:24
β—‹NSns4.markmonitor.com2015-06-20 β†’ 2021-11-06 Β· 4 obs
● 2015-06-20 12:31:00
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
β—‹NSns5.markmonitor.com2015-06-20 β†’ 2021-11-06 Β· 4 obs
● 2015-06-20 12:31:00
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
β—‹NSns6.markmonitor.com2015-06-20 β†’ 2021-11-06 Β· 4 obs
● 2015-06-20 12:31:00
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
β—‹NSns7.markmonitor.com2015-06-20 β†’ 2021-11-06 Β· 4 obs
● 2015-06-20 12:31:00
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
β—‹MX(root)2021-11-06 β†’ 2021-11-06 Β· 3 obs
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
β—‹A108.174.10.142021-11-06 β†’ 2021-11-06 Β· 4 obs
β—‹ 2015-12-13 02:09:02
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
●A108.174.10.242026-03-01 β†’ 2026-03-01 Β· 3 obs
β—‹ 2021-11-06 09:13:26
● 2026-03-01 00:23:22
● 2026-03-01 03:46:24
β—‹A2620:109:c002::6cae:a0e2021-11-06 β†’ 2021-11-06 Β· 4 obs
β—‹ 2015-12-13 02:09:02
● 2021-11-06 09:13:26
β—‹ 2026-03-01 00:23:22
β—‹ 2026-03-01 03:46:24
●A2620:109:c002::6cae:a182026-03-01 β†’ 2026-03-01 Β· 3 obs
β—‹ 2021-11-06 09:13:26
● 2026-03-01 00:23:22
● 2026-03-01 03:46:24
β—‹A72.52.10.142015-06-20 β†’ 2015-11-04 Β· 4 obs
● 2015-06-20 12:31:00
● 2015-11-04 19:47:34
β—‹ 2015-12-13 02:09:02
β—‹ 2026-03-01 03:46:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
inns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info-
linked.inns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org-

βœ… Authoritative Response

Server: 13.107.206.42

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linked.in (unsigned zone)

⏱️ Timing

Total: 414ms | 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)
TXT3h9(0x733378)14lzb7zmz60cjt5mx98w8010cfd, tjl26r6qmn0jfkjjjg2zp4xbby4ln6gr...
SOA1ns1-42.azure-dns.com azuredns-hostmaster

Analysis

IP Addresses

linked.in points to two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.

Other host names, for instance linkedin.it, linkedin.co, linkd.in, careerify.net and linkedinelearning.com share IP numbers with linked.in.

Name Servers

linked.in 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.

linked.in at least partially shares its name servers with other domains, for instance linkedinmobileapp.com, linkedin.kim, linkedinconnect.com, linkedin.my and linkedinmarketing.tools.

These name servers are commonly used with 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.