secure.com.mt - dns.ninja
secure.com.mt
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.bell.net.mt ⭐ | ||||||
| A | 217.168.160.42🇲🇹 ASN-BELLNET217.168.160.0/21 BELLNET-217-168-160/21 | ||||||
| PTR | ns1.bmit.com.mt | ||||||
| PTR | ns1.bell.net.mt | ||||||
| NS | ns2.bell.net.mt | ||||||
| A | 78.110.17.177🇲🇹 ASN-BELLNET78.110.17.0/24 BELLNET-78-110-17/24 | ||||||
| PTR | ns2.bmit.com.mt | ||||||
| PTR | ns2.bell.net.mt | ||||||
| SOA | ns1.bell.net.mthostmaster@bell.net.mt serial=52 | ||||||
com.mt
| DNSSEC | ⚠️ Not signed | ||||||
| NS | a.ns.mt ⭐ ⚠️ Not in parent delegation | ||||||
| NS | b.ns.mt ⚠️ Not in parent delegation | ||||||
| NS | f.ns.mt ⚠️ Not in parent delegation | ||||||
| NS | p.ns.mt ⚠️ Not in parent delegation | ||||||
| SOA | a.ns.mttech@nic.org.mt 2026-06-25 #2 | ||||||
Subdomains
services.secure.com.mt |
Same first word
Similar names
DNS History
2 records (2 active, 0 former)
●NSns1.bell.net.mt2015-06-16 → 2026-06-25 · 2 obs
● 2026-06-25 10:30:34
●NSns2.bell.net.mt2015-06-16 → 2026-06-25 · 2 obs
● 2026-06-25 10:30:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mt | f.ns.mt, b.ns.mt, a.ns.mt, p.ns.mt | 6 records |
| secure.com.mt | ns1.bell.net.mt, ns2.bell.net.mt | - |
✅ Authoritative Response
Server:78.110.17.177
NS records: ns1.bell.net.mt, ns2.bell.net.mt
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mt (unsigned zone)
⏱️ Timing
Total: 1070ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns2.bell.net.mt, ns1.bell.net.mt |
| SOA | 1 | ns1.bell.net.mt hostmaster.bell.net.mt |
📌 Glue Records Collected
Total: 6
In-bailiwick: 6 (a.ns.mt, b.ns.mt, f.ns.mt...)
Analysis
Hierarchy
secure.com.mt serves as the parent of services.secure.com.mt.
Name Servers
Two name servers handle the delegation for secure.com.mt: ns1.bell.net.mt and ns2.bell.net.mt.
secure.com.mt uses the same name servers as several other domains — among them worldmatch.com.mt, 24.110.78.in-addr.arpa, 75.114.37.in-addr.arpa and two more.
secure.com.mt has at least partial name server overlap with other domains, such as 166.168.217.in-addr.arpa, 20.110.78.in-addr.arpa, 171.168.217.in-addr.arpa and two others.
It is common to find these name servers alongside the name servers ns3.bell.net.mt, ns1.bellmed.net, ns2.bellmed.net and two others.
ns1.bell.net.mt directs to 217.168.160.42 and ns2.bell.net.mt directs to 78.110.17.177; each host name points to exactly one IP number.