linkedin-access.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

linkedin-access.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=1786891449

Same first word

linkedin-access.com

DNS History

16 records (6 active, 10 former)

2017201820192020202120222023202420252026NSns1-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:a0e
●NSns1-42.azure-dns.com2026-08-04 → 2026-08-16 · 3 obs
○ 2017-08-29 18:44:56
● 2026-08-04 06:05:14
● 2026-08-16 15:13:10
○NSns1.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
●NSns2-42.azure-dns.net2026-08-04 → 2026-08-16 · 3 obs
○ 2017-08-29 18:44:56
● 2026-08-04 06:05:14
● 2026-08-16 15:13:10
○NSns2.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
●NSns3-42.azure-dns.org2026-08-04 → 2026-08-16 · 3 obs
○ 2017-08-29 18:44:56
● 2026-08-04 06:05:14
● 2026-08-16 15:13:10
○NSns3.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
●NSns4-42.azure-dns.info2026-08-04 → 2026-08-16 · 3 obs
○ 2017-08-29 18:44:56
● 2026-08-04 06:05:14
● 2026-08-16 15:13:10
○NSns4.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
○NSns5.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
○NSns6.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
○NSns7.markmonitor.com2016-12-18 → 2017-08-29 · 4 obs
● 2016-12-18 13:43:46
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
○MX(root)2017-08-29 → 2017-08-29 · 3 obs
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
○A108.174.10.142017-08-29 → 2017-08-29 · 3 obs
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
●A108.174.10.242026-08-04 → 2026-08-16 · 3 obs
○ 2017-08-29 18:44:56
● 2026-08-04 06:05:14
● 2026-08-16 15:13:10
○A2620:109:c002::6cae:a0e2017-08-29 → 2017-08-29 · 3 obs
● 2017-08-29 18:44:56
○ 2026-08-04 06:05:14
○ 2026-08-16 15:13:10
●A2620:109:c002::6cae:a182026-08-04 → 2026-08-16 · 3 obs
○ 2017-08-29 18:44:56
● 2026-08-04 06:05:14
● 2026-08-16 15:13:10

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net...-
linkedin-access.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.10.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 linkedin-access.com (unsigned zone)

⏱️ Timing

Total: 331ms | 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

linkedin-access.com has two IP addresses: 108.174.10.24 and 2620:109:c002::6cae:a18

lingying.com, linked.in, rest.li plus two other host names have IP numbers in common with linkedin-access.com.

Name Servers

Four name servers handle the delegation for linkedin-access.com: 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 linkedin-access.com's name servers are shared with other domains, for example linkedin4business.com, placements.com, linkedin.do 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.

Four host names, each with one IP address: ns1-42.azure-dns.com has 150.171.10.42, ns4-42.azure-dns.info has 13.107.206.42, ns2-42.azure-dns.net has 150.171.16.42 and ns3-42.azure-dns.org has 13.107.222.42.