linkedin.com.bo - robtex.com

linkedin.com.bo

DNSSEC⚠️ Not signed
A2600:1901:0:d5ad::🇺🇸 Google2600:1901::/32
A130.211.32.14🇺🇸 Google130.211.0.0/17
NSdns1.p09.nsone.net
A2620:4d:4000:6259:7:9:0:1🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1
PTRdns1.p09.nsone.net
PTRns4.demysdns.co.uk
A198.51.44.9🇺🇸 NSONE198.51.44.0/24
PTRdns1.p09.nsone.net
PTRns4.demysdns.co.uk
NSdns2.p09.nsone.net
A2a00:edc0:6259:7:9::2🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2
PTRdns2.p09.nsone.net
PTRns5.demysdns.co.uk
A198.51.45.9🇺🇸 NSONE198.51.45.0/24
PTRdns2.p09.nsone.net
PTRns5.demysdns.co.uk
NSdns3.p09.nsone.net ⚠️ Not in parent delegation
A2620:4d:4000:6259:7:9:0:3🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1
PTRdns3.p09.nsone.net
PTRns6.demysdns.co.uk
A198.51.44.73🇺🇸 NSONE198.51.44.0/24
PTRdns3.p09.nsone.net
PTRns6.demysdns.co.uk
NSdns4.p09.nsone.net ⚠️ Not in parent delegation
A2a00:edc0:6259:7:9::4🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2
PTRns7.demysdns.com
PTRdns4.p09.nsone.net
A198.51.45.73🇺🇸 NSONE198.51.45.0/24
PTRns7.demysdns.com
PTRdns4.p09.nsone.net
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 ⚠️ Not in parent delegation
A13.107.222.42🇺🇸 Microsoft13.104.0.0/14 MICROSOFT
PTRns3-42.azure-dns.org
NSns4-42.azure-dns.info ⚠️ Not in parent delegation
A13.107.206.42🇺🇸 Microsoft13.104.0.0/14 MICROSOFT
PTRns4-42.azure-dns.info
TXT_78uh4gjbw3m5czh3cvx6qidrwupx5im
TXT_bqi5f557s4t2gub4ndasj72byuzfgbc
TXTv=spf1 -all
SOAdns1.p09.nsone.nethostmaster@linkedin.com serial=1615923179

com.bo

DNSSEC⚠️ Not signed
WOT: SAFE (61/100)

Same first word

Similar names

DNS History

12 records (10 active, 2 former)

NSdns1.p09.nsone.netdns2.p09.nsone.netdns3.p09.nsone.netdns4.p09.nsone.netns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.infoA130.211.32.142600:1901:0:d5ad::150.171.22.122620:1ec:50::12
NSdns1.p09.nsone.net2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSdns2.p09.nsone.net2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSdns3.p09.nsone.net2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSdns4.p09.nsone.net2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSns1-42.azure-dns.com2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSns2-42.azure-dns.net2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSns3-42.azure-dns.org2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
NSns4-42.azure-dns.info2026-06-24 → 2026-07-30 · 2 obs
● 2026-06-24 10:28:28
● 2026-07-30 23:37:54
A130.211.32.142026-06-25 → 2026-07-30 · 3 obs
○ 2026-06-24 10:28:28
● 2026-06-25 13:15:18
● 2026-07-30 23:37:54
A150.171.22.122026-06-24 → 2026-06-24 · 3 obs
● 2026-06-24 10:28:28
○ 2026-06-25 13:15:18
○ 2026-07-30 23:37:54
A2600:1901:0:d5ad::2026-06-25 → 2026-07-30 · 3 obs
○ 2026-06-24 10:28:28
● 2026-06-25 13:15:18
● 2026-07-30 23:37:54
A2620:1ec:50::122026-06-24 → 2026-06-24 · 3 obs
● 2026-06-24 10:28:28
○ 2026-06-25 13:15:18
○ 2026-07-30 23:37:54

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
boanycast.ns.nic.bo, ns.nic.bo-
linkedin.com.bodns1.p09.nsone.net, ns1-42.azure-dns.com, dns2.p09.nsone.net, ns2-42.azure-dns.net-

✅ Authoritative Response

Server:150.171.16.42

NS records: dns1.p09.nsone.net, ns1-42.azure-dns.com, dns2.p09.nsone.net, ns2-42.azure-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bo (unsigned zone)

⏱️ Timing

Total: 500ms | Queries: -

📄 Records

TypeCountSample Data
A1130.211.32.14
AAAA12600:1901:0:d5ad::
NS8ns1-42.azure-dns.com, ns2-42.azure-dns.net...
MX1. (pri: 0)
TXT3_78uh4gjbw3m5czh3cvx6qidrwupx5im, _bqi5f557s4t2gub4ndasj72byuzfgbc...
SOA1ns1-42.azure-dns.com hostmaster.linkedin

Analysis

IP Addresses

linkedin.com.bo points to the IP addresses 130.211.32.14 and 2600:1901:0:d5ad::

Additional host names — lynda.com, linkedin.com.au, linkedin.co.th and two others — share IP numbers with linkedin.com.bo.

Name Servers

DNS for linkedin.com.bo is handled by 8 name servers: ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and 5 others.

There is at least partial name server overlap between linkedin.com.bo and other domains — thefakenews.com, cbsmediastream.com, beyondbodyyoga.com and two more among them.

These name servers regularly appear alongside dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and 7 other name servers in NS record sets.

Host names with two IP numbers:

dns1.p09.nsone.net has two IP addresses: 198.51.44.9 and 2620:4d:4000:6259:7:9:0:1.

dns2.p09.nsone.net has two IP addresses: 198.51.45.9 and 2a00:edc0:6259:7:9::2.

dns3.p09.nsone.net has two IP addresses: 198.51.44.73 and 2620:4d:4000:6259:7:9:0:3.

dns4.p09.nsone.net has two IP addresses: 198.51.45.73 and 2a00:edc0:6259:7:9::4.

Host names pointing to a single IP address:

ns1-42.azure-dns.com directs to 150.171.10.42.

ns4-42.azure-dns.info directs to 13.107.206.42.

ns2-42.azure-dns.net directs to 150.171.16.42.

ns3-42.azure-dns.org directs to 13.107.222.42.