dmz102.com - robtex.com
dmz102.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 23.231.212.48🇺🇸 ENZU-GLOBAL23.231.192.0/18 Proxy-registered route object | ||||||
| NS | ns1.julydns.com ⭐ | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1777546597 | ||||||
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=1785953074 | ||||||
Same first word
dmz102.com |
Similar names
DNS History
6 records (3 active, 3 former)
○NSf1g1ns1.dnspod.net2019-12-17 → 2019-12-17 · 3 obs
○ 2026-07-13 20:12:22
○ 2026-08-05 18:26:56
○NSf1g1ns2.dnspod.net2019-12-17 → 2019-12-17 · 3 obs
○ 2026-07-13 20:12:22
○ 2026-08-05 18:26:56
●NSns1.julydns.com2026-07-13 → 2026-08-05 · 3 obs
● 2026-07-13 20:12:22
● 2026-08-05 18:26:56
●NSns2.julydns.com2026-07-13 → 2026-08-05 · 3 obs
● 2026-07-13 20:12:22
● 2026-08-05 18:26:56
●A23.231.212.482026-07-13 → 2026-08-05 · 2 obs
● 2026-08-05 18:26:56
○CNAMEdmz102.com.luo278.faipod.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-07-13 20:12:22
○ 2026-08-05 18:26:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| dmz102.com | ns1.julydns.com, ns2.julydns.com | 2 records |
✅ Authoritative Response
Server:162.159.48.223
NS records: ns1.julydns.com, ns2.julydns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dmz102.com (unsigned zone)
⏱️ Timing
Total: 234ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.231.212.48 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)
Analysis
IP Addresses
dmz102.com resolves to just one IP address, 23.231.212.48.
Two other host names, along with h5c.cn, juntu8.com and yzdch.com, also share IP numbers with dmz102.com.
Name Servers
dmz102.com has two authoritative name servers — ns1.julydns.com and ns2.julydns.com.
dmz102.com shares its NS records with other domains, for example salai56.com, (0x736578)ykenya.com, majige.com and two others.
dmz102.com has at least partial name server overlap with other domains, such as jyjczx.com, 23567.cn, lcsale.com and two others.
It is common to find these name servers paired with the name servers ns1.judns.com, ns2.judns.com, ns1.onclouddns.com and ns2.onclouddns.com.
ns1.julydns.com and ns2.julydns.com each point to one IP address — 162.159.48.223.
The host names ns1.julydns.com and ns2.julydns.com both resolve to 162.159.48.223 IP addresses.