`mightycube.co.jp`

DNSSEC	⚠️ Not signed
NS	`01.dnsv.jp` ⭐
		A	2400:8500:3300::53^{🇯🇵 GMO-DNS2400:8500:3300::/48 GMO Internet,inc.}
			PTR	`01.dnsv.jp`
		A	157.7.32.53^{🇯🇵 GMO-DNS157.7.32.0/24 GMO Internet,inc. Network-Team.}
			PTR	`01.dnsv.jp`
NS	`02.dnsv.jp`
		A	157.7.33.53^{🇯🇵 GMO-DNS157.7.33.0/24 GMO Internet,inc. Network-Team.}
			PTR	`02.dnsv.jp`
NS	`03.dnsv.jp`
		A	2400:8500:3000::53^{🇯🇵 GMO-DNS2400:8500:3000::/48 GMO Internet,inc.}
			PTR	`03.dnsv.jp`
		A	157.7.34.53^{🇯🇵 GMO-DNS157.7.34.0/24 GMO Internet,inc. Network-Team.}
			PTR	`03.dnsv.jp`
NS	`04.dnsv.jp`
		A	2400:8500:3fff::53^{🇯🇵 GMO-DNS2400:8500:3fff::/48 GMO Internet,inc.}
			PTR	`04.dnsv.jp`
		A	157.7.35.53^{🇯🇵 GMO-DNS157.7.35.0/24 GMO Internet,inc. Network-Team.}
			PTR	`04.dnsv.jp`
MX	`mightycube-co-jp.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc1a::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1f::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1f::1^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os0p286cu01201.inbound.protection.outlook.com`
		A	2a01:111:f403:cc24::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os0p286cu01300.inbound.protection.outlook.com`
		A	52.101.124.1^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	52.101.124.5^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tyvp286cu00305.inbound.protection.outlook.com`
		A	52.101.157.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os0p286cu01203.inbound.protection.outlook.com`
		A	52.101.157.40^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
TXT	`google-site-verification=gaU4xB8i1X7nUvN0XFzyIyI_0S4wi97EkBZv7UBeljA`
TXT	`v=spf1 include:spf.protection.outlook.com include:spf.mta.hdems.com ~all`
SOA	`01.dnsv.jp`hostmaster@dnsv.jp serial=1718597026

`co.jp`

	DNSSEC	⚠️ Not signed
	TXT	`co.jp.`

WOT: SAFE (58/100)

Same first word

mightycube.com

mightycube.co.jp

DNS History

5 records (5 active, 0 former)

●NS01.dnsv.jp2017-01-18 → 2026-04-24 · 2 obs

● 2017-01-18 05:31:30
● 2026-04-24 15:32:56

●NS02.dnsv.jp2017-01-18 → 2026-04-24 · 2 obs

● 2017-01-18 05:31:30
● 2026-04-24 15:32:56

●NS03.dnsv.jp2017-01-18 → 2026-04-24 · 2 obs

● 2017-01-18 05:31:30
● 2026-04-24 15:32:56

●NS04.dnsv.jp2017-01-18 → 2026-04-24 · 2 obs

● 2017-01-18 05:31:30
● 2026-04-24 15:32:56

●MXmightycube-co-jp.mail.protection.outlook.com2017-01-18 → 2026-04-24 · 2 obs

● 2017-01-18 05:31:30
● 2026-04-24 15:32:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp...	-
mightycube.co.jp	01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp	7 records

✅ Authoritative Response

Server:157.7.35.53

NS records: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mightycube.co.jp (unsigned zone)

⏱️ Timing

Total: 877ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`01.dnsv.jp, 02.dnsv.jp...`
MX	1	`mightycube-co-jp.mail.protection.outlook`
TXT	2	`google-site-verification=gaU4xB8i1X7nUvN, v=spf1 include:spf.protection.outlook.co`
SOA	1	`01.dnsv.jp hostmaster.dnsv.jp`

📌 Glue Records Collected

Total: 7

Out-of-bailiwick: 7 (01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp...)

Analysis

Name Servers

mightycube.co.jp is delegated to four name servers: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp and 04.dnsv.jp.

mightycube.co.jp at least partially shares name servers with other domains, for example 1-navi.net, miu-miu.mobi, al7ewar.net, ewoman.jp and hohoko-style.com.