jdc.dev - dns.ninja
jdc.dev
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 | ||||||
Same first word
Similar names
DNS History
12 records (10 active, 2 former)
●NSns-cloud-b1.googledomains.com2026-02-24 → 2026-07-26 · 3 obs
● 2026-02-24 18:20:06
● 2026-07-26 11:58:16
●NSns-cloud-b2.googledomains.com2026-02-24 → 2026-07-26 · 3 obs
● 2026-02-24 18:20:06
● 2026-07-26 11:58:16
●NSns-cloud-b3.googledomains.com2026-02-24 → 2026-07-26 · 3 obs
● 2026-02-24 18:20:06
● 2026-07-26 11:58:16
●NSns-cloud-b4.googledomains.com2026-02-24 → 2026-07-26 · 3 obs
● 2026-02-24 18:20:06
● 2026-07-26 11:58:16
○NSns1.wuxin.info2020-01-27 → 2020-01-27 · 3 obs
○ 2026-02-24 18:20:06
○ 2026-07-26 11:58:16
●MXalt1.aspmx.l.google.com2026-02-24 → 2026-07-26 · 2 obs
● 2026-07-26 11:58:16
●MXalt2.aspmx.l.google.com2026-02-24 → 2026-07-26 · 2 obs
● 2026-07-26 11:58:16
●MXalt3.aspmx.l.google.com2026-02-24 → 2026-07-26 · 2 obs
● 2026-07-26 11:58:16
●MXalt4.aspmx.l.google.com2026-02-24 → 2026-07-26 · 2 obs
● 2026-07-26 11:58:16
●MXaspmx.l.google.com2026-02-24 → 2026-07-26 · 2 obs
● 2026-07-26 11:58:16
●A75.2.60.52026-02-24 → 2026-07-26 · 2 obs
● 2026-07-26 11:58:16
○CNAMEpark.wuxin.info2020-01-27 → 2020-01-27 · 3 obs
○ 2026-02-24 18:20:06
○ 2026-07-26 11:58:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | 10 records |
| jdc.dev | ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com | - |
✅ Authoritative Response
Server:216.239.34.107
NS records: ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1062ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.2.60.5 |
| NS | 4 | ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-b1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
jdc.dev resolves to just one IP address, 75.2.60.5.
Two other host names, along with c4events.net, indexone.io and daybook.com.au, also share IP numbers with jdc.dev.
Name Servers
The NS records for jdc.dev point to four name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
jdc.dev has at least partial name server overlap with other domains, such as formclinic.com, teeko.com, tsunamiwarningcenter.com and two others.
It is common to see these name servers used together with name servers ns1.mirusresearch.com and ns2.mir.us.
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com all point to exactly two IP numbers each: ns-cloud-b1.googledomains.com → 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com → 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com → 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com → 216.239.38.107 and 2001:4860:4802:38::6b.
Mail Servers
jdc.dev is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between jdc.dev and other domains, including itop.com, mygene.info, server2.theologyweb.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com points to 142.251.111.27 and 2607:f8b0:4004:c19::1a.
alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1b.