`hiroshimamm.com`

DNSSEC	⚠️ Not signed
A	180.222.81.42^{🇯🇵 CPI-NET180.222.80.0/20 KDDI Web Communications Inc.}
		PTR	`bvdeuy42.secure.ne.jp`
NS	`nsk0.secure.ne.jp` ⭐ ⚠️ Not in zone NS records
		A	122.200.212.137^{🇯🇵 CPI-NET122.200.192.0/19}
			PTR	`nsk0.secure.ne.jp`
NS	`ns1.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
NS	`nsk1.secure.ne.jp` ⚠️ Not in zone NS records
		A	122.200.253.229^{🇯🇵 CPI-NET122.200.224.0/19}
			PTR	`nsk1.secure.ne.jp`
MX	`hiroshimamm-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc1a::1^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::2^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00302.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.6^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tyvp286cu00206.inbound.protection.outlook.com`
		A	52.101.157.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os0p286cu01302.inbound.protection.outlook.com`
		A	52.101.157.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os0p286cu01203.inbound.protection.outlook.com`
MX	`vlmx20.secure.ne.jp`⁽¹⁰⁾
		A	111.96.116.216^{🇯🇵 KDDI111.96.0.0/16}
		A	111.96.117.216^{🇯🇵 KDDI111.96.0.0/16}
MX	`vlmx21.secure.ne.jp`⁽¹⁰⁾
		A	111.96.116.216^{🇯🇵 KDDI111.96.0.0/16}
		A	111.96.117.216^{🇯🇵 KDDI111.96.0.0/16}
MX	`vlmx22.secure.ne.jp`⁽²⁰⁾
		A	111.96.116.216^{🇯🇵 KDDI111.96.0.0/16}
		A	111.96.117.216^{🇯🇵 KDDI111.96.0.0/16}
TXT	`MS=ms91041076`
TXT	`seculio-domain-verification-code=35c633d6ee4d8ba17035ded4e4795f2640516af25810...`
TXT	`v=spf1 include:spf.protection.outlook.com include:spf.bmv.jp -all`
TXT	`1password-site-verification=5COSU3U6FRCJNHNH3BVV3XBJKE`
TXT	`apple-domain-verification=PrmkUQHBUpiKp2pS`
SOA	`nsk0.secure.ne.jp`hostmaster@cpi.ad.jp serial=2605070001

`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.net`nstld@verisign-grs.com serial=1784819257

Same first word

hiroshimamm.com

DNS History

13 records (11 active, 2 former)

●NSns1.bdm.microsoftonline.com2017-10-15 → 2026-07-23 · 3 obs

○ 2016-12-17 15:43:18
● 2017-10-15 03:29:46
● 2026-07-23 15:32:00

●NSns2.bdm.microsoftonline.com2017-10-15 → 2026-07-23 · 3 obs

○ 2016-12-17 15:43:18
● 2017-10-15 03:29:46
● 2026-07-23 15:32:00

●NSns3.bdm.microsoftonline.com2017-10-15 → 2026-07-23 · 3 obs

○ 2016-12-17 15:43:18
● 2017-10-15 03:29:46
● 2026-07-23 15:32:00

●NSns4.bdm.microsoftonline.com2017-10-15 → 2026-07-23 · 3 obs

○ 2016-12-17 15:43:18
● 2017-10-15 03:29:46
● 2026-07-23 15:32:00

○NSns6.cpi.ad.jp2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 15:43:18
○ 2017-10-15 03:29:46
○ 2026-07-23 15:32:00

○NSns7.cpi.ad.jp2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 15:43:18
○ 2017-10-15 03:29:46
○ 2026-07-23 15:32:00

●NSnsk0.secure.ne.jp2017-10-15 → 2026-07-23 · 3 obs

○ 2016-12-17 15:43:18
● 2017-10-15 03:29:46
● 2026-07-23 15:32:00

●NSnsk1.secure.ne.jp2026-03-30 → 2026-07-23 · 3 obs

○ 2017-10-15 03:29:46
● 2026-03-30 23:08:00
● 2026-07-23 15:32:00

●MXhiroshimamm-com.mail.protection.outlook.com2017-10-15 → 2026-07-23 · 3 obs

○ 2016-12-17 15:43:18
● 2017-10-15 03:29:46
● 2026-07-23 15:32:00

●MXvlmx20.secure.ne.jp2016-12-17 → 2026-07-23 · 2 obs

● 2016-12-17 15:43:18
● 2026-07-23 15:32:00

●MXvlmx21.secure.ne.jp2016-12-17 → 2026-07-23 · 2 obs

● 2016-12-17 15:43:18
● 2026-07-23 15:32:00

●MXvlmx22.secure.ne.jp2016-12-17 → 2026-07-23 · 2 obs

● 2016-12-17 15:43:18
● 2026-07-23 15:32:00

●A180.222.81.422016-12-17 → 2026-07-23 · 2 obs

● 2016-12-17 15:43:18
● 2026-07-23 15:32:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...	-
hiroshimamm.com	nsk0.secure.ne.jp, nsk1.secure.ne.jp	-

✅ Authoritative Response

Server:122.200.253.229

NS records: nsk0.secure.ne.jp, nsk1.secure.ne.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hiroshimamm.com (unsigned zone)

⏱️ Timing

Total: 2617ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`180.222.81.42`
NS	4	`ns2.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com...`
MX	4	`vlmx21.secure.ne.jp (pri: 10), vlmx20.secure.ne.jp (pri: 10)...`
TXT	5	`seculio-domain-verification-code=35c633d, apple-domain-verification=PrmkUQHBUpiKp2...`
SOA	1	`nsk0.secure.ne.jp hostmaster.cpi.ad.jp`

Analysis

IP Addresses

hiroshimamm.com resolves to one IP address: 180.222.81.42.

Other host names, such as bvdeuy42.secure.ne.jp, share IP numbers with hiroshimamm.com.

Name Servers

hiroshimamm.com is delegated to 6 name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and 3 other.

There is at least partial name server overlap between hiroshimamm.com and other domains — klenmar.com, openlogs.it, duffey.net and two more among them.

The name servers ns4.bdm.microsoftonline.com, nsk0.secure.ne.jp and nsk1.secure.ne.jp are often found in combination with these name servers.

Hostnames that resolve to two IP addresses:

ns1.bdm.microsoftonline.com points to 13.107.236.208 and 2603:1061:0:700::d0.

ns2.bdm.microsoftonline.com points to 150.171.21.208 and 2620:1ec:8ec:700::d0.

ns3.bdm.microsoftonline.com points to 204.14.183.208 and 2a01:111:4000:700::d0.

ns4.bdm.microsoftonline.com points to 208.84.5.208 and 2620:1ec:bda:700::d0.

Hosts with just one IP address:

nsk0.secure.ne.jp points to 122.200.212.137.

nsk1.secure.ne.jp points to 122.200.253.229.