bofa.mw - robtex.com
bofa.mw
mw
| DNSSEC | ⚠️ Not signed | ||||||
| NS | chambo.sdnp.org.mw ⭐ | ||||||
| NS | domwe.sdn.mw | ||||||
| NS | mw-e.ns.nic.cz ⚠️ Not in parent delegation | ||||||
| NS | mw.cctld.authdns.ripe.net ⚠️ Not in parent delegation | ||||||
| NS | ns4.apnic.net ⚠️ Not in parent delegation | ||||||
| NS | pch1.nic.mw | ||||||
| NS | rip.psg.com ⚠️ Not in parent delegation | ||||||
| SOA | chambo.sdnp.org.mwdomains@registrar.mw serial=1786644301 | ||||||
Same first word
Similar names
DNS History
2 records (2 active, 0 former)
●NSns1.netnames.net2026-08-11 → 2026-08-13 · 2 obs
● 2026-08-13 19:02:00
●NSns2.netnames.net2026-08-11 → 2026-08-13 · 2 obs
● 2026-08-13 19:02:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mw | ns4.apnic.net, mw-e.ns.nic.cz, chambo.sdnp.org.mw, mw.cctld.authdns.ripe.net... | 14 records |
| bofa.mw | ns1.netnames.net, ns2.netnames.net | - |
✅ Authoritative Response
Server:156.154.130.100
NS records: ns1.netnames.net, ns2.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mw (unsigned zone)
⏱️ Timing
Total: 777ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.netnames.net, ns2.netnames.net |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
📌 Glue Records Collected
Total: 14
In-bailiwick: 6 (chambo.sdnp.org.mw, chambo.sdnp.org.mw, pch1.nic.mw...)
Out-of-bailiwick: 8 (ns4.apnic.net, ns4.apnic.net, mw-e.ns.nic.cz...)
Analysis
Name Servers
The NS records for bofa.mw delegate to ns1.netnames.net and ns2.netnames.net.
bofa.mw shares its NS records with other domains, for example 113.30.192.in-addr.arpa, componentsource.ch, pse-online.co.uk and two others.
There is at least partial name server overlap between bofa.mw and other domains — webuyanycar.si, hcptaf.com, ehealthinsurancve.com and two more among them.
These name servers regularly appear alongside ns6.netnames.net, ns5.netnames.net, dns1.cscdns.net and 3 other name servers in NS record sets.
ns1.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100. Likewise, ns2.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100 — two IP addresses apiece.