linkedinbot.com - dns.ninja

linkedinbot.com

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
SOAns1-42.azure-dns.comazuredns-hostmaster@microsoft.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=1784206217

Previously MX for

linkedinbot.com

Same first word

linkedinbot.com

DNS History

23 records (6 active, 17 former)

20162017201820192020202120222023202420252026NSns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infokara.ns.cloudflare.comns1.servconfig.comns2.servconfig.comwoz.ns.cloudflare.comMXdc-9a218d92.linkedinbot.comlinkedinbot.commail.linkedinbot.comsecure162.servconfig.comsmtp.linkedinbot.comA108.174.10.242620:109:c002::6cae:a18104.28.22.30104.28.23.30108.174.10.142002:4a7c:d437::4a7c:d4372400:cb00:2048:1::681c:161e2400:cb00:2048:1::681c:171e74.124.212.55
○NSkara.ns.cloudflare.com2015-08-12 → 2016-07-08 · 6 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2026-02-21 14:54:18
○ 2026-07-16 12:57:06
●NSns1-42.azure-dns.com2026-02-21 → 2026-07-16 · 3 obs
○ 2016-07-08 21:19:08
● 2026-02-21 14:54:18
● 2026-07-16 12:57:06
○NSns1.servconfig.com2016-02-27 → 2016-02-27 · 4 obs
○ 2015-11-29 23:38:02
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06
●NSns2-42.azure-dns.net2026-02-21 → 2026-07-16 · 3 obs
○ 2016-07-08 21:19:08
● 2026-02-21 14:54:18
● 2026-07-16 12:57:06
○NSns2.servconfig.com2016-02-27 → 2016-02-27 · 4 obs
○ 2015-11-29 23:38:02
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06
●NSns3-42.azure-dns.org2026-02-21 → 2026-07-16 · 3 obs
○ 2016-07-08 21:19:08
● 2026-02-21 14:54:18
● 2026-07-16 12:57:06
●NSns4-42.azure-dns.info2026-02-21 → 2026-07-16 · 3 obs
○ 2016-07-08 21:19:08
● 2026-02-21 14:54:18
● 2026-07-16 12:57:06
○NSwoz.ns.cloudflare.com2015-08-12 → 2016-07-08 · 6 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2026-02-21 14:54:18
○ 2026-07-16 12:57:06
○MX(root)2020-03-03 → 2020-03-03 · 4 obs
○ 2016-07-08 21:19:08
● 2020-03-03 00:03:08
○ 2026-02-21 14:54:18
○ 2026-07-16 12:57:06
○MXdc-9a218d92.linkedinbot.com2015-08-12 → 2015-11-29 · 4 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
○ 2026-07-16 12:57:06
○MXlinkedinbot.com2016-02-27 → 2016-02-27 · 4 obs
○ 2015-11-29 23:38:02
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06
○MXmail.linkedinbot.com2015-08-12 → 2016-02-27 · 4 obs
● 2015-08-12 06:14:30
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06
○MXsecure162.servconfig.com2016-07-08 → 2016-07-08 · 4 obs
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2020-03-03 00:03:08
○ 2026-07-16 12:57:06
○MXsmtp.linkedinbot.com2015-08-12 → 2016-02-27 · 4 obs
● 2015-08-12 06:14:30
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06
○A104.28.22.302015-08-12 → 2016-07-08 · 6 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2020-03-03 00:03:08
○ 2026-07-16 12:57:06
○A104.28.23.302015-08-12 → 2016-07-08 · 6 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2020-03-03 00:03:08
○ 2026-07-16 12:57:06
○A108.174.10.142020-03-03 → 2020-03-03 · 4 obs
○ 2016-07-08 21:19:08
● 2020-03-03 00:03:08
○ 2026-02-21 14:54:18
○ 2026-07-16 12:57:06
●A108.174.10.242026-02-21 → 2026-07-16 · 3 obs
○ 2020-03-03 00:03:08
● 2026-02-21 14:54:18
● 2026-07-16 12:57:06
○A2002:4a7c:d437::4a7c:d4372016-02-27 → 2016-02-27 · 4 obs
○ 2015-11-29 23:38:02
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06
○A2400:cb00:2048:1::681c:161e2015-08-12 → 2016-07-08 · 6 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2026-02-21 14:54:18
○ 2026-07-16 12:57:06
○A2400:cb00:2048:1::681c:171e2015-08-12 → 2016-07-08 · 6 obs
● 2015-08-12 06:14:30
● 2015-11-29 23:38:02
○ 2016-02-27 00:43:32
● 2016-07-08 21:19:08
○ 2026-02-21 14:54:18
○ 2026-07-16 12:57:06
●A2620:109:c002::6cae:a182026-02-21 → 2026-07-16 · 3 obs
○ 2020-03-03 00:03:08
● 2026-02-21 14:54:18
● 2026-07-16 12:57:06
○A74.124.212.552016-02-27 → 2016-02-27 · 4 obs
○ 2015-11-29 23:38:02
● 2016-02-27 00:43:32
○ 2016-07-08 21:19:08
○ 2026-07-16 12:57:06

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net...-
linkedinbot.comns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com, ns2-42.azure-dns.net1 record

✅ Authoritative Response

Server:150.171.16.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

❌ Bogus (DNSSEC validation failed)

No DNSKEY for linkedinbot.com

⏱️ Timing

Total: 733ms | 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)
TXT1v=spf1 -all
SOA1ns1-42.azure-dns.com azuredns-hostmaster

📌 Glue Records Collected

Total: 1

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

Analysis

IP Addresses

linkedinbot.com has two IP addresses: 108.174.10.24 and 2620:109:c002::6cae:a18

linkedin.co.hu, linkedin.mk, snaphired.com and two other host names share IP numbers with linkedinbot.com.

Name Servers

The authoritative name servers for linkedinbot.com are ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org.

At least some of linkedinbot.com's name servers are shared with other domains, for example linkedin.uk, lnkd-ech3.in, linkedin.design and two more.

These name servers tend to co-occur with dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and 7 other name servers in the same DNS delegations.

Each of the four hosts ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and ns3-42.azure-dns.org points to a single IP address — 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 and ns3-42.azure-dns.org points to 13.107.222.42.