`bpm-database.tokyo`

DNSSEC	⚠️ Not signed
A	240b:12:1840:100:5910:a42a:c5f9:f8df^{🇯🇵 KDDI240b::/26 Japan Network Enabler Corporation}
A	119.240.214.180^{🇯🇵 BIGLOBE119.240.0.0/14 CIDR BLOCK 26}
NS	`ns0.mydns.jp` ⭐
		A	2001:278:1033:4::74:200^{🇯🇵 ODN2001:278::/32 IPv6 BLOCK}
			PTR	`ns0.mydns.jp`
		A	210.197.74.200^{🇯🇵 ODN210.197.0.0/16}
			PTR	`ns0.mydns.jp`
NS	`ns1.mydns.jp`
		A	2001:278:1033:4::74:201^{🇯🇵 ODN2001:278::/32 IPv6 BLOCK}
			PTR	`ns1.mydns.jp`
		A	210.197.74.201^{🇯🇵 ODN210.197.0.0/16}
			PTR	`ns1.mydns.jp`
NS	`ns2.mydns.jp` ⚠️ Not in parent delegation
		A	2001:278:1033:4::74:202^{🇯🇵 ODN2001:278::/32 IPv6 BLOCK}
			PTR	`ns2.mydns.jp`
		A	210.197.74.202^{🇯🇵 ODN210.197.0.0/16}
			PTR	`ns2.mydns.jp`
MX	`bpm-database.tokyo` ⭐
		A	240b:12:1840:100:5910:a42a:c5f9:f8df^{🇯🇵 KDDI240b::/26 Japan Network Enabler Corporation}
		A	119.240.214.180^{🇯🇵 BIGLOBE119.240.0.0/14 CIDR BLOCK 26}
			PTR	`fl1-119-240-214-180.stm.mesh.ad.jp`
TXT	`v=spf1 +ip4:119.240.214.180 +ip6:240b:12:1840:100:5910:a42a:c5f9:f8df a:auth....`
SOA	`ns0.mydns.jp`root@mydns.jp serial=1785514528

`tokyo`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gmoregistry.net` ⭐
	NS	`b.gmoregistry.net`
	NS	`k.gmoregistry.net`
	NS	`l.gmoregistry.net`
	SOA	`a.gmoregistry.net`noc@gmoregistry.net serial=1785529238

Previously NS for

bpm-database.tokyo

MX for

bpm-database.tokyo

Same first word

bpm-database.tokyo

DNS History

11 records (6 active, 5 former)

○NSbpm-database.tokyo2020-02-09 → 2020-02-09 · 3 obs

● 2020-02-09 21:03:50
○ 2026-04-13 02:21:34
○ 2026-07-31 21:08:56

●NSns0.mydns.jp2020-02-09 → 2026-07-31 · 2 obs

● 2020-02-09 21:03:50
● 2026-07-31 21:08:56

●NSns1.mydns.jp2020-02-09 → 2026-07-31 · 2 obs

● 2020-02-09 21:03:50
● 2026-07-31 21:08:56

●NSns2.mydns.jp2020-02-09 → 2026-07-31 · 2 obs

● 2020-02-09 21:03:50
● 2026-07-31 21:08:56

●MXbpm-database.tokyo2020-02-09 → 2026-07-31 · 2 obs

● 2020-02-09 21:03:50
● 2026-07-31 21:08:56

○A118.109.215.832026-04-13 → 2026-07-31 · 2 obs

○ 2026-04-13 02:21:34
○ 2026-07-31 21:08:56

○A119.240.195.252026-04-13 → 2026-06-06 · 5 obs

○ 2020-02-09 21:03:50
● 2026-04-13 02:21:34
● 2026-06-06 08:17:22
○ 2026-06-15 19:01:38
○ 2026-07-31 21:08:56

●A119.240.214.1802026-07-03 → 2026-07-31 · 3 obs

○ 2026-06-15 19:01:38
● 2026-07-03 20:50:04
● 2026-07-31 21:08:56

●A240b:12:1840:100:5910:a42a:c5f9:f8df2026-04-13 → 2026-07-31 · 3 obs

○ 2020-02-09 21:03:50
● 2026-04-13 02:21:34
● 2026-07-31 21:08:56

○A60.237.48.1772026-06-15 → 2026-06-15 · 4 obs

○ 2026-06-06 08:17:22
● 2026-06-15 19:01:38
○ 2026-07-03 20:50:04
○ 2026-07-31 21:08:56

○A60.238.237.22020-02-09 → 2020-02-09 · 3 obs

● 2020-02-09 21:03:50
○ 2026-04-13 02:21:34
○ 2026-07-31 21:08:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tokyo	k.gmoregistry.net, a.gmoregistry.net, l.gmoregistry.net, b.gmoregistry.net	7 records
bpm-database.tokyo	ns1.mydns.jp, ns0.mydns.jp	-

✅ Authoritative Response

Server:210.197.74.201

NS records: ns1.mydns.jp, ns0.mydns.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bpm-database.tokyo (unsigned zone)

⏱️ Timing

Total: 1813ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`119.240.214.180`
AAAA	1	`240b:12:1840:100:5910:a42a:c5f9:f8df`
NS	3	`ns2.mydns.jp, ns0.mydns.jp...`
MX	1	`bpm-database.tokyo (pri: 10)`
TXT	1	`v=spf1 +ip4:119.240.214.180 +ip6:240b:12`
SOA	1	`ns0.mydns.jp root.mydns.jp`

📌 Glue Records Collected

Total: 7

Out-of-bailiwick: 7 (k.gmoregistry.net, a.gmoregistry.net, a.gmoregistry.net...)

Analysis

Mail Server Role

The MX record for bpm-database.tokyo points back to bpm-database.tokyo — it is its own mail server.

IP Addresses

bpm-database.tokyo has two IP addresses: 119.240.214.180 and 240b:12:1840:100:5910:a42a:c5f9:f8df

Name Servers

bpm-database.tokyo has three name servers — ns0.mydns.jp, ns1.mydns.jp and ns2.mydns.jp.

There is at least partial name server overlap between bpm-database.tokyo and other domains — seinolab.jp, rohake.com, nomu.org and two more among them.

Each of ns0.mydns.jp, ns1.mydns.jp and ns2.mydns.jp points to two IP numbers. ns0.mydns.jp points to 210.197.74.200 and 2001:278:1033:4::74:200. ns1.mydns.jp points to 210.197.74.201 and 2001:278:1033:4::74:201. ns2.mydns.jp points to 210.197.74.202 and 2001:278:1033:4::74:202.

Mail Servers

The MX record for bpm-database.tokyo points to a single mail server: bpm-database.tokyo.

bpm-database.tokyo carries two IP numbers: 119.240.214.180 and 240b:12:1840:100:5910:a42a:c5f9:f8df.

bpm-database.tokyo - robtex.com