dz6777.com - robtex.com
dz6777.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2405:1c0:6512:535:1cd4:4d9f:9faa:860🇲🇾 WOODSNET-PH2405:1c0:6512::/48 Customer Route | ||||||
| A | 103.241.114.37🇮🇳 WOODSNET-PH103.241.114.0/24 CMI (Customer Route) | ||||||
| NS | snp2q3l.dz2288cne.com ⭐ | ||||||
| A | 2405:1c0:605e:5229:a134:faf2:9dce:698🇲🇾 WOODSNET-PH2405:1c0:605e::/48 | ||||||
| A | 103.241.11.31🇮🇳 WOODSNET-PH103.241.11.0/24 CMI (Customer Route) | ||||||
| NS | snm1q3l.dz2288cne.com | ||||||
| A | 2405:1c0:6007:d055:9451:3dc2:41e6:895🇲🇾 WOODSNET-PH2405:1c0:6007::/48 | ||||||
| A | 146.88.87.30🇰🇷 WOODSNET-PH146.88.87.0/24 CMI (Customer Route) | ||||||
| NS | snn3q3l.dz2288cne.com | ||||||
| A | 2405:1c0:601e:f8e3:4e7f:237b:5c98:893🇲🇾 WOODSNET-PH2405:1c0:601e::/48 | ||||||
| A | 135.84.241.61🇮🇳 WOODSNET-PH135.84.241.0/24 CMI (Customer Route) | ||||||
| NS | snt4q3l.dz2288cne.com ⚠️ Not in zone NS records | ||||||
| SOA | snp2q3l.dz2288cne.comroot@dz6777.com serial=1608112070 | ||||||
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=1786780944 | ||||||
Same first word
dz6777.com |
DNS History
7 records (6 active, 1 former)
●NSsnm1q3l.dz2288cne.com2016-12-15 → 2026-08-15 · 2 obs
● 2026-08-15 08:12:32
●NSsnn3q3l.dz2288cne.com2016-12-15 → 2026-08-15 · 2 obs
● 2026-08-15 08:12:32
●NSsnp2q3l.dz2288cne.com2016-12-15 → 2026-08-15 · 2 obs
● 2026-08-15 08:12:32
●NSsnt4q3l.dz2288cne.com2016-12-15 → 2026-08-15 · 2 obs
● 2026-08-15 08:12:32
●A103.241.114.372026-08-02 → 2026-08-15 · 3 obs
● 2026-08-02 12:33:30
● 2026-08-15 08:12:32
○A103.252.134.1082016-12-15 → 2017-09-15 · 4 obs
● 2017-09-15 23:38:50
○ 2026-08-02 12:33:30
○ 2026-08-15 08:12:32
●A2405:1c0:6512:535:1cd4:4d9f:9faa:8602026-08-02 → 2026-08-15 · 3 obs
● 2026-08-02 12:33:30
● 2026-08-15 08:12:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| dz6777.com | snm1q3l.dz2288cne.com, snp2q3l.dz2288cne.com, snn3q3l.dz2288cne.com, snt4q3l.dz2288cne.com | 8 records |
✅ Authoritative Response
Server:135.84.241.61
NS records: snm1q3l.dz2288cne.com, snp2q3l.dz2288cne.com, snn3q3l.dz2288cne.com, snt4q3l.dz2288cne.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dz6777.com (unsigned zone)
⏱️ Timing
Total: 652ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.241.114.37 |
| AAAA | 1 | 2405:1c0:6512:535:1cd4:4d9f:9faa:860 |
| NS | 3 | snp2q3l.dz2288cne.com, snm1q3l.dz2288cne.com... |
| SOA | 1 | snp2q3l.dz2288cne.com root.dz6777.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (snm1q3l.dz2288cne.com, snm1q3l.dz2288cne.com, snp2q3l.dz2288cne.com...)
Analysis
IP Addresses
dz6777.com points to the IP addresses 103.241.114.37 and 2405:1c0:6512:535:1cd4:4d9f:9faa:860
Two other host names, along with dz8777.com, dz81005.com and dz733.com, also share IP numbers with dz6777.com.
Name Servers
The NS records for dz6777.com point to four name servers: snm1q3l.dz2288cne.com, snn3q3l.dz2288cne.com, snp2q3l.dz2288cne.com and snt4q3l.dz2288cne.com.
At least some of dz6777.com's name servers are shared with other domains, for example dz551.com, dz873.com, 817vip1.com and two more.
These name servers are often deployed together with the name servers snm1q3l.923923.vip, snn3q3l.923923.vip, snp2q3l.923923.vip and snt4q3l.923923.vip.
snm1q3l.dz2288cne.com resolves to 146.88.87.30 and 2405:1c0:6007:d055:9451:3dc2:41e6:895. snn3q3l.dz2288cne.com resolves to 135.84.241.61 and 2405:1c0:601e:f8e3:4e7f:237b:5c98:893. snp2q3l.dz2288cne.com resolves to 103.241.11.31 and 2405:1c0:605e:5229:a134:faf2:9dce:698. All three hostnames point to two IP numbers each.