cmdb.jp - dns.ninja
cmdb.jp
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1780582502 | ||||||
rank #16624 in the tld
Previously MX for
cmdb.jp |
Same first word
cmdb.cc |
cmdb.net |
cmdb.ro |
cmdb.ca |
cmdb.app |
cmdb.ru |
cmdb.com |
cmdb.co.jp |
cmdb.jp |
cmdb.dk |
cmdb.expert |
cmdb.eu |
cmdb.org |
cmdb.md |
cmdb.de |
cmdb.online |
cmdb.ai |
cmdb.at |
Similar names
DNS History
10 records (5 active, 5 former)
○NSdns01.te-co.co.jp2015-06-05 → 2016-12-05 · 9 obs
○ 2015-10-24 23:38:02
○ 2016-03-13 13:16:32
● 2016-04-03 02:20:38
● 2016-10-04 01:41:14
○ 2016-11-29 01:43:04
● 2016-12-05 16:10:28
○ 2026-02-20 22:15:08
○ 2026-06-04 14:48:06
●NSns-cloud-e1.googledomains.com2026-02-20 → 2026-06-04 · 3 obs
● 2026-02-20 22:15:08
● 2026-06-04 14:48:06
●NSns-cloud-e2.googledomains.com2026-02-20 → 2026-06-04 · 3 obs
● 2026-02-20 22:15:08
● 2026-06-04 14:48:06
●NSns-cloud-e3.googledomains.com2026-02-20 → 2026-06-04 · 3 obs
● 2026-02-20 22:15:08
● 2026-06-04 14:48:06
●NSns-cloud-e4.googledomains.com2026-02-20 → 2026-06-04 · 3 obs
● 2026-02-20 22:15:08
● 2026-06-04 14:48:06
○NSns.cmdb.jp2015-06-05 → 2016-10-04 · 6 obs
○ 2015-10-24 23:38:02
○ 2016-04-03 02:20:38
● 2016-10-04 01:41:14
○ 2016-11-29 01:43:04
○ 2026-06-04 14:48:06
○NSns1.cmdb.jp2015-06-05 → 2016-12-05 · 7 obs
● 2016-03-13 13:16:32
○ 2016-04-03 02:20:38
● 2016-10-04 01:41:14
● 2016-12-05 16:10:28
○ 2026-02-20 22:15:08
○ 2026-06-04 14:48:06
○MXcmdb.jp2015-11-18 → 2016-04-03 · 4 obs
● 2016-04-03 02:20:38
○ 2016-10-04 01:41:14
○ 2026-06-04 14:48:06
●A133.167.212.282026-02-20 → 2026-06-04 · 3 obs
● 2026-02-20 22:15:08
● 2026-06-04 14:48:06
○A49.212.0.1432015-06-05 → 2016-10-04 · 6 obs
● 2016-03-13 13:16:32
○ 2016-04-03 02:20:38
● 2016-10-04 01:41:14
○ 2016-11-29 01:43:04
○ 2026-06-04 14:48:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| cmdb.jp | ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com | - |
✅ Authoritative Response
Server:216.239.32.110
NS records: ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cmdb.jp (unsigned zone)
⏱️ Timing
Total: 1430ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 133.167.212.28 |
| NS | 4 | ns-cloud-e4.googledomains.com, ns-cloud-e2.googledomains.com... |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
Analysis
IP Addresses
cmdb.jp resolves to one IP address: 133.167.212.28.
noso.co.jp, o-mu.com, bee-collect.jp and two other host names share IP numbers with cmdb.jp.
Name Servers
cmdb.jp is served by 4 authoritative name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
cmdb.jp has at least partial name server overlap with other domains, such as reserveprotocol.com, huddlecard.com, mzwatcheslk.com and two others.
ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.