`tokyoengine.co.jp`

DNSSEC	⚠️ Not signed
A	60.43.150.206^{🇯🇵 OCN60.32.0.0/12 (AS4713) CIDR BLOCK 70 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN}
		PTR	`tokyoengine.co.jp`
NS	`mwns1.customer.ne.jp` ⭐
		A	210.150.23.210^{🇯🇵 InfoSphere210.150.0.0/16 INFOSPHERE}
NS	`mwns2.customer.ne.jp`
		A	202.17.152.183^{🇯🇵 InfoSphere202.17.128.0/19 INFOSPHERE}
MX	`mwbgw1.ocn.ad.jp` ⭐
		A	210.145.253.233^{🇯🇵 OCN210.145.0.0/16 (AS4713) CIDR BLOCK 18 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN}
MX	`mwbgw2.ocn.ad.jp` ⭐
		A	210.145.253.234^{🇯🇵 OCN210.145.0.0/16 (AS4713) CIDR BLOCK 18 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN}
TXT	`v=spf1 a include:_spf.bizmw.com ~all`
SOA	`mwns1.customer.ne.jp`host-plan-ac@ntt.com serial=1613874856

`co.jp`

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

WOT: SAFE (58/100)

PTR for

206.150.43.60.in-addr.arpa

Subdomains

www.tokyoengine.co.jp

Same first word

tokyoengine.co.jp

tokyoengine.click

DNS History

13 records (5 active, 8 former)

●NSmwns1.customer.ne.jp2026-06-22 → 2026-08-03 · 3 obs

○ 2017-07-04 19:56:28
● 2026-06-22 19:37:36
● 2026-08-03 16:04:32

●NSmwns2.customer.ne.jp2026-06-22 → 2026-08-03 · 3 obs

○ 2017-07-04 19:56:28
● 2026-06-22 19:37:36
● 2026-08-03 16:04:32

○NSns-207.dns.jp-e1.cloudn-service.com2016-03-10 → 2017-07-04 · 5 obs

○ 2015-12-01 09:27:38
● 2016-03-10 18:43:46
● 2017-07-04 19:56:28
○ 2026-06-22 19:37:36
○ 2026-08-03 16:04:32

○NSns-208.dns.jp-w1.cloudn-service.com2016-03-10 → 2017-07-04 · 5 obs

○ 2015-12-01 09:27:38
● 2016-03-10 18:43:46
● 2017-07-04 19:56:28
○ 2026-06-22 19:37:36
○ 2026-08-03 16:04:32

○NSns-209.dns.us-e1.cloudn-service.com2016-03-10 → 2017-07-04 · 5 obs

○ 2015-12-01 09:27:38
● 2016-03-10 18:43:46
● 2017-07-04 19:56:28
○ 2026-06-22 19:37:36
○ 2026-08-03 16:04:32

○NSns1.secure.net2015-07-15 → 2015-12-01 · 4 obs

● 2015-07-15 20:43:52
● 2015-12-01 09:27:38
○ 2016-03-10 18:43:46
○ 2026-08-03 16:04:32

○NSns2.secure.net2015-07-15 → 2015-12-01 · 4 obs

● 2015-07-15 20:43:52
● 2015-12-01 09:27:38
○ 2016-03-10 18:43:46
○ 2026-08-03 16:04:32

○MXin.sjc.mx.trendmicro.com2015-07-15 → 2015-07-15 · 3 obs

● 2015-07-15 20:43:52
○ 2015-12-01 09:27:38
○ 2026-08-03 16:04:32

●MXmwbgw1.ocn.ad.jp2015-12-01 → 2026-08-03 · 3 obs

○ 2015-07-15 20:43:52
● 2015-12-01 09:27:38
● 2026-08-03 16:04:32

●MXmwbgw2.ocn.ad.jp2015-12-01 → 2026-08-03 · 3 obs

○ 2015-07-15 20:43:52
● 2015-12-01 09:27:38
● 2026-08-03 16:04:32

○A153.254.30.622015-07-15 → 2015-07-15 · 3 obs

● 2015-07-15 20:43:52
○ 2015-12-01 09:27:38
○ 2026-08-03 16:04:32

●A60.43.150.2062026-06-22 → 2026-08-03 · 3 obs

○ 2017-07-04 19:56:28
● 2026-06-22 19:37:36
● 2026-08-03 16:04:32

○A60.43.179.1912015-12-01 → 2017-07-04 · 5 obs

○ 2015-07-15 20:43:52
● 2015-12-01 09:27:38
● 2017-07-04 19:56:28
○ 2026-06-22 19:37:36
○ 2026-08-03 16:04:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	d.dns.jp, g.dns.jp, h.dns.jp, f.dns.jp...	-
tokyoengine.co.jp	mwns1.customer.ne.jp, mwns2.customer.ne.jp	-

✅ Authoritative Response

Server:210.150.23.210

NS records: mwns1.customer.ne.jp, mwns2.customer.ne.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 1035ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`60.43.150.206`
NS	2	`mwns1.customer.ne.jp, mwns2.customer.ne.jp`
MX	2	`mwbgw1.ocn.ad.jp (pri: 10), mwbgw2.ocn.ad.jp (pri: 10)`
TXT	1	`v=spf1 a include:_spf.bizmw.com ~all`
SOA	1	`mwns1.customer.ne.jp host-plan-ac.ntt.co`

Analysis

Hierarchy

tokyoengine.co.jp serves as the parent of www.tokyoengine.co.jp.

IP Addresses

tokyoengine.co.jp resolves to one IP address: 60.43.150.206.

Name Servers

Two name servers handle the delegation for tokyoengine.co.jp: mwns1.customer.ne.jp and mwns2.customer.ne.jp.

tokyoengine.co.jp uses the same name servers as several other domains — among them esaki.ecnet.jp, jp-towa.com, estrela.co.jp and two more.

mwns1.customer.ne.jp directs to 210.150.23.210 and mwns2.customer.ne.jp directs to 202.17.152.183; each host name points to exactly one IP number.

Mail Servers

Mail for tokyoengine.co.jp is handled by two mail servers — mwbgw1.ocn.ad.jp and mwbgw2.ocn.ad.jp.

tokyoengine.co.jp uses an identical mail server configuration to several other domains — among them utaka.jp, gakushikai.or.jp, hibarigaoka-hp.jp and two more.

mwbgw1.ocn.ad.jp directs to 210.145.253.233 and mwbgw2.ocn.ad.jp directs to 210.145.253.234; each host name points to exactly one IP number.

tokyoengine.co.jp - robtex.com