securitylinkedin.nl - robtex.com

securitylinkedin.nl

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

nl

DNSSECπŸ”’ Signed (DS record present)
NSns1.dns.nl ⭐
NSns3.dns.nl
NSns4.dns.nl
TXTnl zone update: 2026-05-03 01:30:02 +0000 (EPOCH 1777771802)
SOAns1.dns.nldns@sidn.nl 2026-05-03 #3

Same first word

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:a0e93.191.168.52
●NSns1-42.azure-dns.com2026-04-09 β†’ 2026-05-03 Β· 3 obs
β—‹ 2018-06-24 23:47:58
● 2026-04-09 23:18:24
● 2026-05-03 02:18:24
β—‹NSns1.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
●NSns2-42.azure-dns.net2026-04-09 β†’ 2026-05-03 Β· 3 obs
β—‹ 2018-06-24 23:47:58
● 2026-04-09 23:18:24
● 2026-05-03 02:18:24
β—‹NSns2.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
●NSns3-42.azure-dns.org2026-04-09 β†’ 2026-05-03 Β· 3 obs
β—‹ 2018-06-24 23:47:58
● 2026-04-09 23:18:24
● 2026-05-03 02:18:24
β—‹NSns3.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
●NSns4-42.azure-dns.info2026-04-09 β†’ 2026-05-03 Β· 3 obs
β—‹ 2018-06-24 23:47:58
● 2026-04-09 23:18:24
● 2026-05-03 02:18:24
β—‹NSns4.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
β—‹NSns5.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
β—‹NSns6.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
β—‹NSns7.markmonitor.com2015-07-06 β†’ 2018-06-24 Β· 4 obs
● 2015-07-06 23:04:40
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
β—‹MX(root)2018-06-24 β†’ 2018-06-24 Β· 3 obs
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
β—‹A108.174.10.142018-06-24 β†’ 2018-06-24 Β· 4 obs
β—‹ 2016-12-31 12:18:54
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
●A108.174.10.242026-04-09 β†’ 2026-05-03 Β· 3 obs
β—‹ 2018-06-24 23:47:58
● 2026-04-09 23:18:24
● 2026-05-03 02:18:24
β—‹A2620:109:c002::6cae:a0e2018-06-24 β†’ 2018-06-24 Β· 4 obs
β—‹ 2016-12-31 12:18:54
● 2018-06-24 23:47:58
β—‹ 2026-04-09 23:18:24
β—‹ 2026-05-03 02:18:24
●A2620:109:c002::6cae:a182026-04-09 β†’ 2026-05-03 Β· 3 obs
β—‹ 2018-06-24 23:47:58
● 2026-04-09 23:18:24
● 2026-05-03 02:18:24
β—‹A93.191.168.522015-07-06 β†’ 2016-12-31 Β· 4 obs
● 2015-07-06 23:04:40
● 2016-12-31 12:18:54
β—‹ 2018-06-24 23:47:58
β—‹ 2026-05-03 02:18:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
nlns1.dns.nl, ns3.dns.nl, ns4.dns.nl-
securitylinkedin.nlns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info, ns1-42.azure-dns.com-

βœ… Authoritative Response

Server:150.171.16.42

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securitylinkedin.nl (unsigned zone)

⏱️ Timing

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

Analysis

IP Addresses

securitylinkedin.nl points to two IP numbers: 2620:109:c002::6cae:a18 and 108.174.10.24.

Other host names such as refressh.me, linkedin.at, linkedin.lv, linkedin.lu and linkedin.it share IP numbers with securitylinkedin.nl.

Name Servers

securitylinkedin.nl 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.

At least part of the name servers for securitylinkedin.nl are shared with other domains, for instance lnkedin.com, gridwiki.com, linkedin.at, linkedin.com.pe and linkedin.lv.

these name servers are commonly used with the name servers 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: 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.