code-wave.app - robtex.com
code-wave.app
app
| DNSSEC | π Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com β | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=101427 | ||||||
Same first word
code-wave.app |
code-wave.net |
code-wave.de |
code-wave.workers.dev |
code-wave.co.uk |
code-wave.store |
code-wave.co.kr |
code-wave.pages.dev |
code-wave.pro |
Similar names
Previous names
Next names
DNS History
5 records (5 active, 0 former)
βNSns1hwy.name.com2026-10-11 β 2026-11-08 Β· 2 obs
β 2026-11-08 20:13:54
βNSns2fln.name.com2026-10-11 β 2026-11-08 Β· 2 obs
β 2026-11-08 20:13:54
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| app | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| code-wave.app | ns1hwy.name.com, ns3fqs.name.com, ns2fln.name.com, ns4jnz.name.com | - |
β Authoritative Response
Server:163.114.217.49
NS records: ns1hwy.name.com, ns3fqs.name.com, ns2fln.name.com, ns4jnz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for code-wave.app (unsigned zone)
β±οΈ Timing
Total: 1963ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1hwy.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
Delegation for code-wave.app is to five name servers: ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
At least some of code-wave.app's name servers are shared with other domains, for example zero.tel, thedailybourse.com, kelsiegames.com and two more.
These name servers tend to co-occur with ns3fqs.name.com, ns4jnz.name.com, ns4lpv.name.com and 4 other name servers in the same DNS delegations.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1hwy.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1hwy.name.com resolve to 163.114.216.17 IP addresses each.