java-diamond.com - dns.ninja
java-diamond.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.nonverifieddomain.com ⚠️ Not in zone NS records | ||||||
| NS | ns2.nonverifieddomain.com ⚠️ Not in zone NS records | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1794014106 | ||||||
Same first word
java-diamond.com |
Previous names
Next names
DNS History
18 records (2 active, 16 former)
○NSignacio.ns.cloudflare.com2026-10-07 → 2026-10-07 · 4 obs
● 2026-10-07 10:18:20
○ 2026-10-27 21:15:16
○ 2026-11-07 01:30:00
○NSns.dnspropagation.com2015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
●NSns1.nonverifieddomain.com2026-10-27 → 2026-11-07 · 3 obs
● 2026-10-27 21:15:16
● 2026-11-07 01:30:00
○NSns1626.ztomy.com2017-11-15 → 2017-11-15 · 4 obs
● 2017-11-15 01:29:32
○ 2026-10-07 10:18:20
○ 2026-11-07 01:30:00
○NSns2.dnspropagation.com2015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
●NSns2.nonverifieddomain.com2026-10-27 → 2026-11-07 · 3 obs
● 2026-10-27 21:15:16
● 2026-11-07 01:30:00
○NSns2626.ztomy.com2017-11-15 → 2017-11-15 · 4 obs
● 2017-11-15 01:29:32
○ 2026-10-07 10:18:20
○ 2026-11-07 01:30:00
○NSvenus.ns.cloudflare.com2026-10-07 → 2026-10-07 · 4 obs
● 2026-10-07 10:18:20
○ 2026-10-27 21:15:16
○ 2026-11-07 01:30:00
○MXalt1.aspmx.l.google.com2015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
○MXalt2.aspmx.l.google.com2015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
○MXaspmx.l.google.com2015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
○MXaspmx2.googlemail.com2015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
○MXroute1.mx.cloudflare.net2026-10-07 → 2026-10-07 · 4 obs
● 2026-10-07 10:18:20
○ 2026-10-27 21:15:16
○ 2026-11-07 01:30:00
○MXroute2.mx.cloudflare.net2026-10-07 → 2026-10-07 · 4 obs
● 2026-10-07 10:18:20
○ 2026-10-27 21:15:16
○ 2026-11-07 01:30:00
○MXroute3.mx.cloudflare.net2026-10-07 → 2026-10-07 · 4 obs
● 2026-10-07 10:18:20
○ 2026-10-27 21:15:16
○ 2026-11-07 01:30:00
○A204.11.56.482017-11-15 → 2017-11-15 · 4 obs
● 2017-11-15 01:29:32
○ 2026-10-07 10:18:20
○ 2026-11-07 01:30:00
○A69.162.107.262015-07-05 → 2016-12-26 · 4 obs
● 2016-12-26 12:48:44
○ 2017-11-15 01:29:32
○ 2026-11-07 01:30:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| java-diamond.com | ns1.nonverifieddomain.com, ns2.nonverifieddomain.com | 2 records |
✅ Authoritative Response
Server:47.75.3.214
NS records: ns1.nonverifieddomain.com, ns2.nonverifieddomain.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: 641ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.nonverifieddomain.com, ns2.nonverifieddomain.com)
Analysis
Name Servers
java-diamond.com uses two name servers for its delegation: ns1.nonverifieddomain.com and ns2.nonverifieddomain.com.
java-diamond.com uses the same name servers as several other domains — among them baranmehr.com, ptcitius.com, jo-malonedeutschland.com and two more.
At least some of java-diamond.com's name servers are shared with other domains, for example lunitnor.com, aktivitaten-ppl.com, mhtindonesia.com and two more.
These name servers tend to be deployed in combination with the name servers ns1.ezydomain.com and ns2.ezydomain.com.