linkedn.com - dns.ninja

linkedn.com

DNSSEC⚠️ Not signed
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
TXT_a9emmey146od8gll24rwkgciw778gum
TXTv=spf1 -all
SOAns1-42.azure-dns.comhostmaster@linkedin.com serial=1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1783232391

Same first word

linkedn.co
linkedn.social
linkedn.com
linkedn.org
linkedn.net
linkedn.nl

Similar names

dklinen.com
neklind.se
kinndle.com
lindken.com
lendink.com
nkiendl.net
enkindl.com
nlinked.com
nedlink.mobi
denlink.net
nedlink.co.za
inklend.com
endlink.com
linkden.com
denlink.com
lindken.de
kniendl.at
knedlin.com
nedlink.be
dnelkin.com
lindenk.com
ndkline.com
linnked.com
nedlink.org
lindken.net
lnkedin.com
nkindle.com
linkned.com
linendk.com
inkedln.com
nedlink.nl
nedlink.com
lnkedin.eu

DNS History

14 records (4 active, 10 former)

200920112013201520172019202120232025NSns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infons1.lamedelegation.netns1.markmonitor.comns2.lamedelegation.netns2.markmonitor.comns3.markmonitor.comns4.markmonitor.comns5.markmonitor.comns6.markmonitor.comns7.markmonitor.comA209.62.20.188
●NSns1-42.azure-dns.com2026-04-08 → 2026-07-05 · 3 obs
○ 2017-08-15 19:00:48
● 2026-04-08 00:12:58
● 2026-07-05 06:24:20
○NSns1.lamedelegation.net2008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 23:37:42
○ 2015-08-17 05:57:48
○ 2026-07-05 06:24:20
○NSns1.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
●NSns2-42.azure-dns.net2026-04-08 → 2026-07-05 · 3 obs
○ 2017-08-15 19:00:48
● 2026-04-08 00:12:58
● 2026-07-05 06:24:20
○NSns2.lamedelegation.net2008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 23:37:42
○ 2015-08-17 05:57:48
○ 2026-07-05 06:24:20
○NSns2.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
●NSns3-42.azure-dns.org2026-04-08 → 2026-07-05 · 3 obs
○ 2017-08-15 19:00:48
● 2026-04-08 00:12:58
● 2026-07-05 06:24:20
○NSns3.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
●NSns4-42.azure-dns.info2026-04-08 → 2026-07-05 · 3 obs
○ 2017-08-15 19:00:48
● 2026-04-08 00:12:58
● 2026-07-05 06:24:20
○NSns4.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
○NSns5.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
○NSns6.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
○NSns7.markmonitor.com2015-08-17 → 2017-08-15 · 5 obs
○ 2008-03-19 23:37:42
● 2015-08-17 05:57:48
● 2017-08-15 19:00:48
○ 2026-04-08 00:12:58
○ 2026-07-05 06:24:20
○A209.62.20.1882008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 23:37:42
○ 2015-08-17 05:57:48
○ 2026-07-05 06:24:20

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net...-
linkedn.comns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net1 record

✅ Authoritative Response

Server:13.107.206.42

NS records: 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 linkedn.com (unsigned zone)

⏱️ Timing

Total: 1914ms | Queries: -

📄 Records

TypeCountSample Data
NS4ns1-42.azure-dns.com, ns2-42.azure-dns.net...
MX1. (pri: 0)
TXT2v=spf1 -all, _a9emmey146od8gll24rwkgciw778gum
SOA1ns1-42.azure-dns.com hostmaster.linkedin

📌 Glue Records Collected

Total: 1

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

Analysis

Name Servers

The domain linkedn.com is delegated to these four name servers: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.

linkedn.com shares at least some of its name servers with other domains, including linkedin.ba, linkedinseg.cn, lynda.jp and two others.

These name servers are frequently seen alongside dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and 7 other name servers.

ns1-42.azure-dns.com resolves to 150.171.10.42. ns4-42.azure-dns.info resolves to 13.107.206.42. ns2-42.azure-dns.net resolves to 150.171.16.42. ns3-42.azure-dns.org resolves to 13.107.222.42. All four hosts carry exactly one IP address.