code88code.com - robtex.com
code88code.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=1788094460 | ||||||
Same first word
code88code.com |
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A185.158.133.12026-08-19 → 2026-08-30 · 2 obs
● 2026-08-30 12:59:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net... | - |
| code88code.com | ns1hwy.name.com, ns2fln.name.com, ns3fqs.name.com, ns4jnz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1hwy.name.com, ns2fln.name.com, ns3fqs.name.com, ns4jnz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for code88code.com (unsigned zone)
⏱️ Timing
Total: 219ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.158.133.1 |
| NS | 4 | ns1hwy.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1hwy.name.com, ns1hwy.name.com, ns2fln.name.com...)
Analysis
IP Addresses
code88code.com resolves to one IP address: 185.158.133.1.
databesa.com, progressx.app, future-mama.com and two other host names share IP numbers with code88code.com.
Name Servers
code88code.com has five name servers, which are ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
There is at least partial name server overlap between code88code.com and other domains — voyeurnightclub.com, onliar.life, easycashing.net and two more among them.
These name servers regularly appear alongside ns4jnz.name.com, ns3fqs.name.com, ns1cnb.name.com and 7 other name servers in NS record sets.
Hostnames that resolve to two IP addresses:
ns1.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com maps to two IP addresses — 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com maps to two IP addresses — 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.name.com maps to two IP addresses — 163.114.217.49 and 2402:cf80:107::49.
These two host names — ns1.name.com and ns1hwy.name.com — each point to 2a00:edc0:107::1 IP addresses.
These two host names — ns1.name.com and ns1hwy.name.com — each point to 163.114.216.17 IP addresses.