dmzone.com - dns.ninja
dmzone.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.45.246.141🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094 | ||||||
| NS | ns1.domainrecover.com ⭐ | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns2.domainrecover.com | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| PTR | 199.247.16.62.vultrusercontent.com | ||||||
| TXT | yGjyZf7SHD | ||||||
| SOA | ns1.domainrecover.comhostmaster@domainreover.com serial=1623031840 | ||||||
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=1782829731 | ||||||
Same first word
Similar names
DNS History
12 records (3 active, 9 former)
○NShost.tradenames.com2015-10-27 → 2016-04-02 · 4 obs
● 2016-04-02 13:07:28
○ 2016-08-09 17:45:04
○ 2026-06-30 14:31:48
○NSns.tradenames.com2015-10-27 → 2016-04-02 · 4 obs
● 2016-04-02 13:07:28
○ 2016-08-09 17:45:04
○ 2026-06-30 14:31:48
●NSns1.domainrecover.com2026-06-30 → 2026-06-30 · 3 obs
● 2026-06-30 00:12:32
● 2026-06-30 14:31:48
○NSns1.dsredirection.com2016-08-09 → 2016-08-09 · 4 obs
● 2016-08-09 17:45:04
○ 2017-04-02 16:29:42
○ 2026-06-30 14:31:48
●NSns2.domainrecover.com2026-06-30 → 2026-06-30 · 3 obs
● 2026-06-30 00:12:32
● 2026-06-30 14:31:48
○NSns2.dsredirection.com2016-08-09 → 2016-08-09 · 4 obs
● 2016-08-09 17:45:04
○ 2017-04-02 16:29:42
○ 2026-06-30 14:31:48
○A141.8.230.202016-08-09 → 2017-04-02 · 5 obs
● 2016-08-09 17:45:04
● 2017-04-02 16:29:42
○ 2020-03-29 08:21:06
○ 2026-06-30 14:31:48
○A66.45.246.1402015-10-27 → 2016-04-02 · 4 obs
● 2016-04-02 13:07:28
○ 2016-08-09 17:45:04
○ 2026-06-30 14:31:48
●A66.45.246.1412026-06-30 → 2026-06-30 · 3 obs
● 2026-06-30 00:12:32
● 2026-06-30 14:31:48
○CNAMEpres.serverhome.com2016-08-09 → 2017-04-02 · 4 obs
● 2017-04-02 16:29:42
○ 2020-03-29 08:21:06
○ 2026-06-30 14:31:48
○CNAMEsnews.serverhome.com2020-03-29 → 2020-03-29 · 4 obs
● 2020-03-29 08:21:06
○ 2026-06-30 00:12:32
○ 2026-06-30 14:31:48
○CNAMEthie5ku9.dsgeneration.com2016-08-09 → 2016-08-09 · 3 obs
○ 2017-04-02 16:29:42
○ 2026-06-30 14:31:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| dmzone.com | ns1.domainrecover.com, ns2.domainrecover.com | 2 records |
✅ Authoritative Response
Server:149.248.38.58
NS records: ns1.domainrecover.com, ns2.domainrecover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dmzone.com (unsigned zone)
⏱️ Timing
Total: 441ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.45.246.141 |
| NS | 2 | NS2.DOMAINRECOVER.com, NS1.DOMAINRECOVER.com |
| TXT | 1 | yGjyZf7SHD |
| SOA | 1 | ns1.domainrecover.com hostmaster.domainr |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)
Analysis
IP Addresses
dmzone.com resolves to one IP address: 66.45.246.141.
securetex.com, otterbean.com, castledata.com and two other host names share IP numbers with dmzone.com.
Name Servers
dmzone.com uses two name servers for its delegation: ns1.domainrecover.com and ns2.domainrecover.com.
dmzone.com uses the same name servers as several other domains — among them escapin.com, koloss.com, getwap.com and two more.
dmzone.com shares at least some of its name servers with other domains, including promem.com, xaleo.com, elkalaa.com and two others.
These name servers are frequently seen alongside the name servers ns1.serverhome.com, ns2.serverhome.com, ns2.servering.com and ns.servering.com.
ns1.domainrecover.com and ns2.domainrecover.com each resolve to one IP number: ns1.domainrecover.com points to 149.248.38.58 and ns2.domainrecover.com points to 199.247.16.62.