valid8tr.com - robtex.com
valid8tr.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=1786214709 | ||||||
Same first word
valid8tr.com |
DNS History
6 records (6 active, 0 former)
●A91.195.240.942026-04-07 → 2026-08-08 · 2 obs
● 2026-08-08 19:01:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| valid8tr.com | ns1cvw.name.com, ns2fwz.name.com, ns3dkz.name.com, ns4hmp.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.49
NS records: ns1cvw.name.com, ns2fwz.name.com, ns3dkz.name.com, ns4hmp.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for valid8tr.com (unsigned zone)
⏱️ Timing
Total: 242ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1cvw.name.com, ns2fwz.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1cvw.name.com, ns1cvw.name.com, ns2fwz.name.com...)
Analysis
IP Addresses
valid8tr.com resolves to just one IP address, 91.195.240.94.
Two other host names, along with ditu.demilovato.org, is-pas.com and whydrone.com, also share IP numbers with valid8tr.com.
Name Servers
valid8tr.com delegates to five name servers: ns1.name.com, ns1cvw.name.com, ns2fwz.name.com and two others.
valid8tr.com partially shares its NS delegation with several other domains, including solutionwebltd.net, patientconversions.info, starviewrupert.com and two others.
In DNS configurations, these name servers often share authority with ns3dkz.name.com, ns4hmp.name.com, ns2kry.name.com and 7 other name servers.
Host names that have two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1cvw.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2fwz.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3dkz.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4hmp.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1cvw.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1cvw.name.com resolve to 163.114.216.17 IP addresses each.