zaneperforapi.com - robtex.com
zaneperforapi.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=1771291435 | ||||||
MX for
zaneperforapi.com |
Same first word
zaneperforapi.com |
DNS History
7 records (7 active, 0 former)
βNSns1ksz.name.com2026-02-21 β 2026-02-21 Β· 2 obs
β 2026-02-21 04:43:24
βNSns2cvx.name.com2026-02-21 β 2026-02-21 Β· 2 obs
β 2026-02-21 04:43:24
βNSns3jnr.name.com2026-02-21 β 2026-02-21 Β· 2 obs
β 2026-02-21 04:43:24
βNSns4qxz.name.com2026-02-21 β 2026-02-21 Β· 2 obs
β 2026-02-21 04:43:24
βMXzaneperforapi.com2026-02-21 β 2026-02-21 Β· 2 obs
β 2026-02-21 04:43:24
βA209.38.85.442026-02-21 β 2026-02-21 Β· 2 obs
β 2026-02-21 04:43:24
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net... | - |
| zaneperforapi.com | ns1ksz.name.com, ns2cvx.name.com, ns3jnr.name.com, ns4qxz.name.com | 8 records |
β Authoritative Response
Server: 163.114.217.17
NS records: ns1ksz.name.com, ns2cvx.name.com, ns3jnr.name.com, ns4qxz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for zaneperforapi.com (unsigned zone)
β±οΈ Timing
Total: 196ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 209.38.85.44 |
| NS | 4 | ns1ksz.name.com, ns2cvx.name.com... |
| MX | 1 | zaneperforapi.com (pri: 10) |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1ksz.name.com, ns1ksz.name.com, ns2cvx.name.com...)
AI analysis
zaneperforapi.com serves as a mail server for zaneperforapi.com.
zaneperforapi.com points to a single IP: 209.38.85.44.
zaneperforapi.com is delegated to five name servers: ns1.name.com, ns1ksz.name.com, ns2cvx.name.com, ns3jnr.name.com and ns4qxz.name.com.
zaneperforapi.com partially shares name servers with other domains; examples include asteco.net, lecakery.in, tupakula.com, openkyiv.com and groopes.com.
These name servers are commonly used alongside ns4cjp.name.com, ns3dty.name.com, ns1cnb.name.com, ns3cna.name.com, ns1kwy.name.com, ns4lny.name.com, ns1hwy.name.com, ns1kpv.name.com, ns1ntw.name.com and ns3bfm.name.com.
Host names with two IP numbers:
ns1.name.com points to 2a00:edc0:107::1 and 163.114.216.17
ns1ksz.name.com points to 2a00:edc0:107::1 and 163.114.216.17
ns2cvx.name.com points to 2402:cf80:107::1 and 163.114.216.49
ns3jnr.name.com points to 2a00:edc0:107::49 and 163.114.217.17
ns4qxz.name.com points to 2402:cf80:107::49 and 163.114.217.49
Names pointing to 2a00:edc0:107::1: ns1.name.com and ns1ksz.name.com
Names pointing to 163.114.216.17: ns1.name.com and ns1ksz.name.com
zaneperforapi.com is handled by a single mail server, zaneperforapi.com.
zaneperforapi.com points to a single IP: 209.38.85.44.