linkedin.be - robtex.com

linkedin.be

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
TXT3pms0stlqdmqv6q0v22bkb6tjspygx72
TXTmj1gwn57s0q3dvdsrxbs5xr2ncl06ww8
TXTv=spf1 -all
SOAns1-42.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

be

DNSSECπŸ”’ Signed (DS record present)
NSa.nsset.be ⭐
NSb.nsset.be
NSc.nsset.be
NSd.nsset.be
NSy.nsset.be
NSz.nsset.be
SOAa.nsset.bebe-hostmaster@dnsbelgium.be serial=1028244812

Same first word

Similar names

DNS History

26 records (6 active, 20 former)

20162017201820192020202120222023202420252026NSns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infons1.linkedin.comns1.markmonitor.comns1.p43.dynect.netns2.linkedin.comns2.markmonitor.comns2.p43.dynect.netns3.linkedin.comns3.markmonitor.comns3.p43.dynect.netns4.markmonitor.comns5.markmonitor.comns6.markmonitor.comns7.markmonitor.comMXmail-c.linkedin.commail.linkedin.comA108.174.10.242620:109:c002::6cae:a18108.174.10.14108.174.2.133199.101.163.1332620:109:c002::6cae:a0e
●NSns1-42.azure-dns.com2026-02-18 β†’ 2026-05-09 Β· 3 obs
β—‹ 2020-09-13 17:44:22
● 2026-02-18 06:44:20
● 2026-05-09 15:06:10
β—‹NSns1.linkedin.com2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹NSns1.markmonitor.com2016-03-17 β†’ 2017-06-03 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2017-06-03 08:50:00
β—‹ 2019-10-18 11:25:16
β—‹ 2026-05-09 15:06:10
β—‹NSns1.p43.dynect.net2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
●NSns2-42.azure-dns.net2026-02-18 β†’ 2026-05-09 Β· 3 obs
β—‹ 2020-09-13 17:44:22
● 2026-02-18 06:44:20
● 2026-05-09 15:06:10
β—‹NSns2.linkedin.com2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹NSns2.markmonitor.com2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹NSns2.p43.dynect.net2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
●NSns3-42.azure-dns.org2026-02-18 β†’ 2026-05-09 Β· 3 obs
β—‹ 2020-09-13 17:44:22
● 2026-02-18 06:44:20
● 2026-05-09 15:06:10
β—‹NSns3.linkedin.com2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹NSns3.markmonitor.com2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹NSns3.p43.dynect.net2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
●NSns4-42.azure-dns.info2026-02-18 β†’ 2026-05-09 Β· 3 obs
β—‹ 2020-09-13 17:44:22
● 2026-02-18 06:44:20
● 2026-05-09 15:06:10
β—‹NSns4.markmonitor.com2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹NSns5.markmonitor.com2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹NSns6.markmonitor.com2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹NSns7.markmonitor.com2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹MX(root)2019-10-18 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-03-17 03:42:46
● 2019-10-18 11:25:16
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
β—‹MXmail-c.linkedin.com2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹MXmail.linkedin.com2015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹A108.174.10.142016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
●A108.174.10.242026-02-18 β†’ 2026-05-09 Β· 3 obs
β—‹ 2020-09-13 17:44:22
● 2026-02-18 06:44:20
● 2026-05-09 15:06:10
β—‹A108.174.2.1332015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹A199.101.163.1332015-08-03 β†’ 2016-01-06 Β· 4 obs
● 2015-08-03 15:40:02
● 2016-01-06 23:37:56
β—‹ 2016-03-17 03:42:46
β—‹ 2026-05-09 15:06:10
β—‹A2620:109:c002::6cae:a0e2016-03-17 β†’ 2020-09-13 Β· 5 obs
β—‹ 2016-01-06 23:37:56
● 2016-03-17 03:42:46
● 2020-09-13 17:44:22
β—‹ 2026-02-18 06:44:20
β—‹ 2026-05-09 15:06:10
●A2620:109:c002::6cae:a182026-02-18 β†’ 2026-05-09 Β· 3 obs
β—‹ 2020-09-13 17:44:22
● 2026-02-18 06:44:20
● 2026-05-09 15:06:10

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
bea.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be...-
linkedin.bens1-42.azure-dns.com, ns2-42.azure-dns.net, ns3-42.azure-dns.org, ns4-42.azure-dns.info-

βœ… Authoritative Response

Server:150.171.10.42

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkedin.be (unsigned zone)

⏱️ Timing

Total: 1220ms | 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)
TXT33pms0stlqdmqv6q0v22bkb6tjspygx72, mj1gwn57s0q3dvdsrxbs5xr2ncl06ww8...
SOA1ns1-42.azure-dns.com azuredns-hostmaster

Analysis

IP Addresses

linkedin.be points to two IPs: 2620:109:c002::6cae:a18 and 108.174.10.24.

Other host names, for instance linkedinbenefits.com, compilr.net, linkedin.de, reffresh.me and linkedin.bg share IP numbers with linkedin.be.

Name Servers

linkedin.be 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.

linkedin.be at least partially shares name servers with other domains such as 161.101.199.in-addr.arpa, hrtech.co, linkedin.estate, iris.claims and linkedin-idb2.com.

These name servers are often used together 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