`clearfile-direct.jp`

DNSSEC	⚠️ Not signed
A	202.231.241.249^{🇯🇵 BEKKOAME202.231.192.0/18 INTERNET INC.}
NS	`nsx1.mitene.ad.jp` ⭐
		A	218.219.161.1^{🇯🇵 MITENE-NET218.219.160.0/19 PACNET (proxy-registered route object)}
			PTR	`nsx1.mitene.ad.jp`
NS	`nsx2.mitene.ad.jp`
		A	218.219.162.122^{🇯🇵 MITENE-NET218.219.160.0/19 PACNET (proxy-registered route object)}
			PTR	`nsx2.mitene.ad.jp`
MX	`mx-0.mitene.jp` ⭐
		A	210.134.182.27^{🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object)}
MX	`mx-1.mitene.jp`⁽²⁰⁾
		A	210.134.182.28^{🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object)}
MX	`mx.mitene.jp`⁽²⁰⁾
		A	210.134.182.26^{🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object)}
TXT	`v=spf1 mx include:spf.aams5.jp ip4:61.119.123.98 ip4:61.119.123.99 ip4:210.22...`
SOA	`nsx1.mitene.ad.jp`postmaster@po.mitene.or.jp 2012-04-16 #16

`jp`

	DNSSEC	🔒 Signed (DS record present)
	NS	`z.dns.jp` ⭐
	NS	`a.dns.jp`
	NS	`b.dns.jp`
	NS	`c.dns.jp`
	NS	`d.dns.jp`
	NS	`e.dns.jp`
	NS	`f.dns.jp`
	NS	`g.dns.jp`
	NS	`h.dns.jp`
	SOA	`z.dns.jp`root@dns.jp serial=1774651503

Same first word

clearfile-direct.jp

DNS History

9 records (6 active, 3 former)

●NSnsx1.mitene.ad.jp2015-07-25 → 2026-03-27 · 2 obs

● 2015-07-25 07:24:16
● 2026-03-27 23:05:50

●NSnsx2.mitene.ad.jp2015-07-25 → 2026-03-27 · 2 obs

● 2015-07-25 07:24:16
● 2026-03-27 23:05:50

○MXmail.clearfile-direct.jp2015-07-25 → 2016-01-25 · 4 obs

● 2015-07-25 07:24:16
● 2016-01-25 11:55:40
○ 2016-04-11 11:13:28
○ 2026-03-27 23:05:50

●MXmx-0.mitene.jp2016-04-11 → 2026-03-27 · 3 obs

○ 2016-01-25 11:55:40
● 2016-04-11 11:13:28
● 2026-03-27 23:05:50

●MXmx-1.mitene.jp2016-04-11 → 2026-03-27 · 3 obs

○ 2016-01-25 11:55:40
● 2016-04-11 11:13:28
● 2026-03-27 23:05:50

●MXmx.mitene.jp2016-04-11 → 2026-03-27 · 3 obs

○ 2016-01-25 11:55:40
● 2016-04-11 11:13:28
● 2026-03-27 23:05:50

○A202.231.241.2472016-04-11 → 2017-06-29 · 5 obs

○ 2016-01-25 11:55:40
● 2016-04-11 11:13:28
● 2017-06-29 08:59:50
○ 2026-03-22 11:07:18
○ 2026-03-27 23:05:50

●A202.231.241.2492026-03-22 → 2026-03-27 · 3 obs

○ 2017-06-29 08:59:50
● 2026-03-22 11:07:18
● 2026-03-27 23:05:50

○A210.227.37.1802015-07-25 → 2016-01-25 · 4 obs

● 2015-07-25 07:24:16
● 2016-01-25 11:55:40
○ 2016-04-11 11:13:28
○ 2026-03-27 23:05:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	b.dns.jp, e.dns.jp, d.dns.jp, c.dns.jp...	-
clearfile-direct.jp	nsx1.mitene.ad.jp, nsx2.mitene.ad.jp	2 records

✅ Authoritative Response

Server:218.219.161.1

NS records: nsx1.mitene.ad.jp, nsx2.mitene.ad.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for clearfile-direct.jp (unsigned zone)

⏱️ Timing

Total: 793ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`202.231.241.249`
NS	2	`nsx2.mitene.ad.jp, nsx1.mitene.ad.jp`
MX	3	`mx-0.mitene.jp (pri: 20), mx.mitene.jp (pri: 10)...`
TXT	1	`v=spf1 mx include:spf.aams5.jp ip4:61.11`
SOA	1	`nsx1.mitene.ad.jp postmaster.po.mitene.o`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (nsx2.mitene.ad.jp, nsx1.mitene.ad.jp)

Analysis

IP Addresses

clearfile-direct.jp maps to IP address 202.231.241.249.

Other host names for instance calendar-direct.jp and www.calendar-direct.jp share IP numbers with clearfile-direct.jp.

Name Servers

Two name servers nsx1.mitene.ad.jp and nsx2.mitene.ad.jp are delegated to clearfile-direct.jp.

clearfile-direct.jp uses the same name server configuration as other domains, such as 158.213.220.in-addr.arpa, 13.241.124.in-addr.arpa, 61.238.202.in-addr.arpa, 161.213.220.in-addr.arpa and 102.213.220.in-addr.arpa.

clearfile-direct.jp at least partially shares name servers with other domains such as hondalf.co.jp, yasukawa-hospital.jp, town.eiheiji.lg.jp, mtn.co.jp and ccu.jp.