miztasand.com - robtex.com
miztasand.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=1783468386 | ||||||
Same first word
miztasand.com |
DNS History
5 records (5 active, 0 former)
βNSns1kpv.name.com2026-07-08 β 2026-07-08 Β· 2 obs
β 2026-07-08 00:20:26
βNSns2kry.name.com2026-07-08 β 2026-07-08 Β· 2 obs
β 2026-07-08 00:20:26
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| miztasand.com | ns1kpv.name.com, ns2kry.name.com, ns3jmt.name.com, ns4dmx.name.com | 8 records |
β Authoritative Response
Server:163.114.217.17
NS records: ns1kpv.name.com, ns2kry.name.com, ns3jmt.name.com, ns4dmx.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for miztasand.com (unsigned zone)
β±οΈ Timing
Total: 367ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1kpv.name.com, ns2kry.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1kpv.name.com, ns1kpv.name.com, ns2kry.name.com...)
Analysis
Name Servers
Five name servers handle delegation for miztasand.com: ns1.name.com, ns1kpv.name.com, ns2kry.name.com and two others.
miztasand.com shares at least some of its name servers with other domains, including healthzap.co, meszaros.in, 111821.com and two others.
These name servers are frequently seen alongside ns4dmx.name.com, ns3jmt.name.com, ns3dkz.name.com and 7 other name servers.
Host names pointing to two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1kpv.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2kry.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3jmt.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4dmx.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1kpv.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1kpv.name.com each resolve to 163.114.216.17 IP addresses.