4aanm7.com - robtex.com
4aanm7.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=1786338819 | ||||||
Same first word
4aanm7.com |
DNS History
5 records (5 active, 0 former)
βNSns1cnb.name.com2026-03-12 β 2026-08-10 Β· 2 obs
β 2026-08-10 05:25:08
βNSns2qvz.name.com2026-03-12 β 2026-08-10 Β· 2 obs
β 2026-08-10 05:25:08
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net... | - |
| 4aanm7.com | ns2qvz.name.com, ns4qxz.name.com, ns3cna.name.com, ns1cnb.name.com | 8 records |
β Authoritative Response
Server:163.114.216.17
NS records: ns2qvz.name.com, ns4qxz.name.com, ns3cna.name.com, ns1cnb.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for 4aanm7.com (unsigned zone)
β±οΈ Timing
Total: 213ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns2qvz.name.com, ns4qxz.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns2qvz.name.com, ns2qvz.name.com, ns4qxz.name.com...)
Analysis
Name Servers
4aanm7.com has five name servers, which are ns1.name.com, ns1cnb.name.com, ns2qvz.name.com and two others.
At least some of 4aanm7.com's name servers are shared with other domains, for example 02rkcv.com, bb93.com, countryclubhyderabad.com and two more.
These name servers tend to co-occur with ns3cna.name.com, ns4qxz.name.com, ns4bht.name.com and 7 other name servers in the same DNS delegations.
Hostnames that resolve to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1cnb.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2qvz.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3cna.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4qxz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1cnb.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1cnb.name.com resolve to 163.114.216.17 IP addresses each.