domdistrict.com - robtex.com
domdistrict.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774763167 | ||||||
Previously MX for
domdistrict.com |
Subdomains
Same first word
domdistrict.com |
DNS History
9 records (4 active, 5 former)
●NSns1.dyna-ns.net2026-02-16 → 2026-03-29 · 3 obs
● 2026-02-16 16:53:26
● 2026-03-29 05:48:22
○NSns1.dynadot.com2015-07-11 → 2017-04-18 · 4 obs
● 2017-04-18 17:21:36
○ 2026-02-16 16:53:26
○ 2026-03-29 05:48:22
●NSns2.dyna-ns.net2026-02-16 → 2026-03-29 · 3 obs
● 2026-02-16 16:53:26
● 2026-03-29 05:48:22
○NSns2.dynadot.com2015-07-11 → 2017-04-18 · 4 obs
● 2017-04-18 17:21:36
○ 2026-02-16 16:53:26
○ 2026-03-29 05:48:22
○MXdomdistrict.com2015-07-11 → 2017-04-18 · 4 obs
● 2017-04-18 17:21:36
○ 2026-02-16 16:53:26
○ 2026-03-29 05:48:22
●MXvps-5520a8d5.vps.ovh.us2026-02-16 → 2026-03-29 · 3 obs
● 2026-02-16 16:53:26
● 2026-03-29 05:48:22
●A51.81.187.262026-02-16 → 2026-03-29 · 3 obs
● 2026-02-16 16:53:26
● 2026-03-29 05:48:22
○A64.91.229.2122017-04-18 → 2026-02-16 · 5 obs
● 2017-04-18 17:21:36
● 2026-02-16 16:53:26
○ 2026-02-20 17:51:00
○ 2026-03-29 05:48:22
○A64.91.230.552015-07-11 → 2016-07-09 · 4 obs
● 2016-07-09 12:36:06
○ 2017-04-18 17:21:36
○ 2026-03-29 05:48:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, i.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net... | - |
| domdistrict.com | ns2.dyna-ns.net, ns1.dyna-ns.net | - |
✅ Authoritative Response
Server:162.159.24.5
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for domdistrict.com (unsigned zone)
⏱️ Timing
Total: 523ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 51.81.187.26 |
| NS | 2 | ns1.dyna-ns.net, ns2.dyna-ns.net |
| MX | 1 | vps-5520a8d5.vps.ovh.us (pri: 0) |
| TXT | 1 | v=spf1 a mx ip4:51.81.187.26 ~all |
| SOA | 1 | ns1.dyna-ns.net hostmaster.domdistrict.c |
Analysis
Hierarchy
The parent of ns3.domdistrict.com, host.domdistrict.com and ns1.domdistrict.com is domdistrict.com.
IP Addresses
domdistrict.com points to an IP address: 51.81.187.26.
Other host names, such as genetic.dv2.com, dv2.com and vps-5520a8d5.vps.ovh.us, share IP numbers with domdistrict.com.
Name Servers
Two name servers ns1.dyna-ns.net and ns2.dyna-ns.net handle the delegation for domdistrict.com.
domdistrict.com shares the same name server setup as other domains, for instance zebim.com, acessending.com, watadot.com, oc.tel and videosgay(0x706f726e).com.
Host names with four IP numbers:
ns1.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158.
ns2.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.
Mail Servers
domdistrict.com is handled by a single mail server, vps-5520a8d5.vps.ovh.us.
vps-5520a8d5.vps.ovh.us resolves to two IPs: 2604:2dc0:202:300::f and 51.81.187.26.