codexat.com - dns.ninja
codexat.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=1781032838 | ||||||
Subdomains
Same first word
codexat.com |
Similar names
DNS History
5 records (5 active, 0 former)
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net... | - |
| codexat.com | ns1bcp.name.com, ns2fgp.name.com, ns3gnv.name.com, ns4cjp.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1bcp.name.com, ns2fgp.name.com, ns3gnv.name.com, ns4cjp.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for codexat.com (unsigned zone)
⏱️ Timing
Total: 195ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1bcp.name.com, ns2fgp.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1bcp.name.com, ns1bcp.name.com, ns2fgp.name.com...)
Analysis
Hierarchy
dns1.codexat.com and dns2.codexat.com are both subdomains of codexat.com.
Name Servers
codexat.com delegates to 5 name servers — ns1.name.com, ns1bcp.name.com and ns2fgp.name.com among them, along with two more.
codexat.com partially shares its NS delegation with several other domains, including alleyelashes.com, craftyourstartup.com, joounzb.com and two others.
It is common to see these name servers paired with ns4cjp.name.com, ns3gnv.name.com, ns3fgh.name.com and seven other name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1bcp.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2fgp.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gnv.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4cjp.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1bcp.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1bcp.name.com resolve to 163.114.216.17 IP addresses each.