linkedin.com.mt - robtex.com

linkedin.com.mt

DNSSEC⚠️ Not signed
A2620:1ec:50::12πŸ‡ΊπŸ‡Έ Microsoft2620:1ec::/36 MICROSOFT
A150.171.22.12πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
NSns1-42.azure-dns.com ⭐
A150.171.10.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
NSdns1.p09.nsone.net
A2620:4d:4000:6259:7:9:0:1πŸ‡ΊπŸ‡Έ NSONE2620:4d:4000::/48 2620:4D:4000::/48
PTRdns1.p09.nsone.net
PTRns4.demysdns.co.uk
A198.51.44.9πŸ‡ΊπŸ‡Έ NSONE198.51.44.0/24 198.51.44.0
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 198.51.45.0
PTRdns2.p09.nsone.net
PTRns5.demysdns.co.uk
NSdns3.p09.nsone.net
A2620:4d:4000:6259:7:9:0:3πŸ‡ΊπŸ‡Έ NSONE2620:4d:4000::/48 2620:4D:4000::/48
PTRdns3.p09.nsone.net
PTRns6.demysdns.co.uk
A198.51.44.73πŸ‡ΊπŸ‡Έ NSONE198.51.44.0/24 198.51.44.0
PTRdns3.p09.nsone.net
PTRns6.demysdns.co.uk
NSdns4.p09.nsone.net
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 198.51.45.0
PTRns7.demysdns.com
PTRdns4.p09.nsone.net
NSns2-42.azure-dns.net
A150.171.16.42πŸ‡ΊπŸ‡Έ Microsoft150.171.0.0/16 MICROSOFT
NSns3-42.azure-dns.org
A13.107.222.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
NSns4-42.azure-dns.info
A13.107.206.42πŸ‡ΊπŸ‡Έ Microsoft13.104.0.0/14 MICROSOFT
TXT_bqi5f557s4t2gub4ndasj72byuzfgbc
TXTv=spf1 -all
SOAns1-42.azure-dns.comhostmaster@linkedin.com serial=9

com.mt

DNSSEC⚠️ Not signed
NSa.ns.mt ⭐ ⚠️ Not in parent delegation
NSb.ns.mt ⚠️ Not in parent delegation
NSf.ns.mt ⚠️ Not in parent delegation
NSp.ns.mt ⚠️ Not in parent delegation
SOAa.ns.mttech@nic.org.mt 2026-06-09 #4
WOT: SAFE (50/100)

Same first word

Similar names

DNS History

10 records (10 active, 0 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.infoA150.171.22.122620:1ec:50::12
●NSdns1.p09.nsone.net2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSdns2.p09.nsone.net2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSdns3.p09.nsone.net2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSdns4.p09.nsone.net2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSns1-42.azure-dns.com2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSns2-42.azure-dns.net2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSns3-42.azure-dns.org2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●NSns4-42.azure-dns.info2026-05-21 β†’ 2026-06-09 Β· 2 obs
● 2026-05-21 12:52:18
● 2026-06-09 14:55:26
●A150.171.22.122026-06-09 β†’ 2026-06-09 Β· 1 obs
● 2026-06-09 14:55:26
●A2620:1ec:50::122026-06-09 β†’ 2026-06-09 Β· 1 obs
● 2026-06-09 14:55:26

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
mta.ns.mt, b.ns.mt, f.ns.mt, p.ns.mt6 records
linkedin.com.mtdns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net...-

βœ… Authoritative Response

Server:13.107.206.42

NS records: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, 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 mt (unsigned zone)

⏱️ Timing

Total: 518ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1150.171.22.12
AAAA12620:1ec:50::12
NS8ns1-42.azure-dns.com, ns2-42.azure-dns.net...
MX1. (pri: 0)
TXT2_bqi5f557s4t2gub4ndasj72byuzfgbc, v=spf1 -all
SOA1ns1-42.azure-dns.com hostmaster.linkedin

πŸ“Œ Glue Records Collected

Total: 6

In-bailiwick: 6 (a.ns.mt, b.ns.mt, f.ns.mt...)

Analysis

IP Addresses

linkedin.com.mt points to two IP numbers: 150.171.22.12 and 2620:1ec:50::12.

Two other host names, along with mumbo.com, linkedin.com.mx and rapportive.com, also share IP numbers with linkedin.com.mt.

Name Servers

Delegation for linkedin.com.mt covers 8 name servers, including ns1-42.azure-dns.com, ns4-42.azure-dns.info, ns2-42.azure-dns.net and five others.

linkedin.com.mt shares at least some of its name servers with other domains, including beviacom.pl, warlockschallenge.com, usalenterprises.com and two others.

These name servers co-occur with dns2.p09.nsone.net, dns1.p09.nsone.net, dns3.p09.nsone.net and seven other name servers on a regular basis.

Host names that have two IP addresses:

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 with one IP number:

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.