mitacap.com - dns.ninja
mitacap.com
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=1782766611 | ||||||
Same first word
mitacap.com |
Similar names
DNS History
12 records (5 active, 7 former)
●NSmaster.dns.ne.jp2026-02-26 → 2026-06-29 · 3 obs
● 2026-02-26 09:15:18
● 2026-06-29 20:57:30
●NSns1.dns.ne.jp2026-02-26 → 2026-06-29 · 3 obs
● 2026-02-26 09:15:18
● 2026-06-29 20:57:30
●NSns2.dns.ne.jp2026-02-26 → 2026-06-29 · 3 obs
● 2026-02-26 09:15:18
● 2026-06-29 20:57:30
○NSns2.dnsdun.com2017-10-13 → 2017-10-13 · 4 obs
● 2017-10-13 01:08:54
○ 2026-02-26 09:15:18
○ 2026-06-29 20:57:30
○NSns2.dnsdun.net2017-10-13 → 2017-10-13 · 4 obs
● 2017-10-13 01:08:54
○ 2026-02-26 09:15:18
○ 2026-06-29 20:57:30
○NSns63.domaincontrol.com2016-12-20 → 2016-12-20 · 3 obs
○ 2017-10-13 01:08:54
○ 2026-06-29 20:57:30
○NSns64.domaincontrol.com2016-12-20 → 2016-12-20 · 3 obs
○ 2017-10-13 01:08:54
○ 2026-06-29 20:57:30
●MXmitacap-com.mail.eo.outlook.com2026-02-26 → 2026-06-29 · 3 obs
● 2026-02-26 09:15:18
● 2026-06-29 20:57:30
○MXmitacap-com.mail.protection.outlook.com2016-12-20 → 2016-12-20 · 3 obs
○ 2017-10-13 01:08:54
○ 2026-06-29 20:57:30
●A133.167.29.882026-02-26 → 2026-06-29 · 3 obs
● 2026-02-26 09:15:18
● 2026-06-29 20:57:30
○A160.153.136.32016-12-20 → 2016-12-20 · 3 obs
○ 2017-10-13 01:08:54
○ 2026-06-29 20:57:30
○A160.202.67.602017-10-13 → 2017-10-13 · 4 obs
● 2017-10-13 01:08:54
○ 2026-02-26 09:15:18
○ 2026-06-29 20:57:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net... | - |
| mitacap.com | ns1.dns.ne.jp, ns2.dns.ne.jp | - |
✅ Authoritative Response
Server:133.167.21.1
NS records: ns1.dns.ne.jp, ns2.dns.ne.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mitacap.com (unsigned zone)
⏱️ Timing
Total: 1121ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 133.167.29.88 |
| NS | 2 | ns1.dns.ne.jp, ns2.dns.ne.jp |
| MX | 1 | mitacap-com.mail.eo.outlook.com (pri: 1) |
| TXT | 2 | MS=ms88664037, v=spf1 +ip4:210.128.34.159 +ip4:210.133. |
| SOA | 1 | master.dns.ne.jp tech.sakura.ad.jp |
Analysis
IP Addresses
mitacap.com has exactly one IP address — 133.167.29.88.
Host names such as mitasec.com and 88.29.167.133.static.www3138.sakura.ne.jp share IP numbers with mitacap.com.
Name Servers
mitacap.com is delegated to three name servers: master.dns.ne.jp, ns1.dns.ne.jp and ns2.dns.ne.jp.
mitacap.com shares at least some of its name servers with other domains, including thepowercap.net, s-shinri.sakura.ne.jp, rioworksco.com and two others.
master.dns.ne.jp, ns1.dns.ne.jp and ns2.dns.ne.jp each resolve to a single IP address: master.dns.ne.jp resolves to 210.224.172.18, ns1.dns.ne.jp resolves to 61.211.236.1 and ns2.dns.ne.jp resolves to 133.167.21.1.
Mail Servers
mitacap.com uses one mail server — mitacap-com.mail.eo.outlook.com.
mitacap-com.mail.eo.outlook.com has 8 IP addresses: 52.101.124.5, 52.101.157.10, 52.101.157.11 plus 5 more.