forgecore.dev - dns.ninja
forgecore.dev
| DNSSEC | ⚠️ Not signed | ||||||
| NS | buck.ns.cloudflare.com ⭐ | ||||||
| NS | lily.ns.cloudflare.com | ||||||
| SOA | buck.ns.cloudflare.comdns@cloudflare.com serial=2417839276 | ||||||
dev
| 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=1 | ||||||
DNS History
2 records (2 active, 0 former)
●NSbuck.ns.cloudflare.com2026-10-04 → 2026-10-19 · 2 obs
● 2026-10-04 01:36:06
● 2026-10-19 23:54:54
● 2026-10-19 23:54:54
●NSlily.ns.cloudflare.com2026-10-04 → 2026-10-19 · 2 obs
● 2026-10-04 01:36:06
● 2026-10-19 23:54:54
● 2026-10-19 23:54:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld5.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | 10 records |
| forgecore.dev | lily.ns.cloudflare.com, buck.ns.cloudflare.com | - |
✅ Authoritative Response
Server:172.64.32.130
NS records: lily.ns.cloudflare.com, buck.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)
⏱️ Timing
Total: 1175ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | buck.ns.cloudflare.com, lily.ns.cloudflare.com |
| SOA | 1 | buck.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
DNS delegation for forgecore.dev points to two name servers: buck.ns.cloudflare.com and lily.ns.cloudflare.com.