forgeclient.dev - dns.ninja
forgeclient.dev
| DNSSEC | ⚠️ Not signed | ||||||
| A | 54.215.31.113Amazon54.215.0.0/17 | ||||||
| NS | ns1.dyna-ns.net ⭐ | ||||||
| NS | ns2.dyna-ns.net | ||||||
| SOA | ns1.dyna-ns.nethostmaster@forgeclient.dev 2026-09-30 #2 | ||||||
dev
| DNSSEC | ⚠️ Not signed | ||||||
| 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=1 | ||||||
Same first word
forgeclient.com |
forgeclient.net |
forgeclient.io |
forgeclient.dev |
Similar names
DNS History
3 records (3 active, 0 former)
●NSns1.dyna-ns.net2026-10-01 → 2026-10-30 · 2 obs
● 2026-10-01 05:09:08
● 2026-10-30 07:18:52
● 2026-10-30 07:18:52
●NSns2.dyna-ns.net2026-10-01 → 2026-10-30 · 2 obs
● 2026-10-01 05:09:08
● 2026-10-30 07:18:52
● 2026-10-30 07:18:52
●A54.215.31.1132026-10-01 → 2026-10-30 · 2 obs
● 2026-10-01 05:09:08
● 2026-10-30 07:18:52
● 2026-10-30 07:18:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| forgeclient.dev | ns1.dyna-ns.net, ns2.dyna-ns.net | - |
✅ Authoritative Response
Server:162.159.27.158
NS records: ns1.dyna-ns.net, ns2.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for forgeclient.dev (unsigned zone)
⏱️ Timing
Total: 953ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.215.31.113 |
| NS | 2 | ns1.dyna-ns.net, ns2.dyna-ns.net |
| SOA | 1 | ns1.dyna-ns.net hostmaster.forgeclient.d |
Analysis
IP Addresses
forgeclient.dev has exactly one IP address — 54.215.31.113.
Name Servers
forgeclient.dev has two authoritative name servers — ns1.dyna-ns.net and ns2.dyna-ns.net.