deckengine.app - robtex.com
deckengine.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
deckengine.ai |
deckengine.app |
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A185.158.133.12026-09-01 → 2026-09-04 · 2 obs
● 2026-09-04 06:49:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| app | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| deckengine.app | ns3fqs.name.com, ns1hwy.name.com, ns2fln.name.com, ns4jnz.name.com | - |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns3fqs.name.com, ns1hwy.name.com, ns2fln.name.com, ns4jnz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for deckengine.app (unsigned zone)
⏱️ Timing
Total: 1041ms | 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 |
Analysis
IP Addresses
deckengine.app has exactly one IP address — 185.158.133.1.
novra.trimarkcreatives.com, lasernorazor.co.uk, creatorshive.online plus two other host names have IP numbers in common with deckengine.app.
Name Servers
Five name servers handle delegation for deckengine.app: ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
deckengine.app shares at least some of its name servers with other domains, including zentaiskin.com, zigula.com, verify.pet and two others.
These name servers are frequently seen alongside ns4jnz.name.com, ns3fqs.name.com, ns1cnb.name.com and 7 other name servers.
Host names pointing to two IP addresses:
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.