`accomplishincreade.tokyo`

DNSSEC	⚠️ Not signed
A	122.215.92.116^{🇯🇵 UCOM122.212.0.0/14 ARTERIA Networks Corporation(UCOM)}
		PTR	`122x215x92x116.ap122.ftth.ucom.ne.jp`
NS	`ns1.accomplishincreade.tokyo` ⭐
		A	122.215.92.116^{🇯🇵 UCOM122.212.0.0/14 ARTERIA Networks Corporation(UCOM)}
			PTR	`122x215x92x116.ap122.ftth.ucom.ne.jp`
NS	`ns2.accomplishincreade.tokyo`
		A	122.215.92.116^{🇯🇵 UCOM122.212.0.0/14 ARTERIA Networks Corporation(UCOM)}
			PTR	`122x215x92x116.ap122.ftth.ucom.ne.jp`
MX	`mx1.accomplishincreade.tokyo` ⭐
		A	122.215.92.116^{🇯🇵 UCOM122.212.0.0/14 ARTERIA Networks Corporation(UCOM)}
			PTR	`122x215x92x116.ap122.ftth.ucom.ne.jp`
MX	`mx2.accomplishincreade.tokyo`⁽²⁰⁾
		A	122.215.92.116^{🇯🇵 UCOM122.212.0.0/14 ARTERIA Networks Corporation(UCOM)}
			PTR	`122x215x92x116.ap122.ftth.ucom.ne.jp`
TXT	`v=spf1 ~all`
SOA	`ns1.accomplishincreade.tokyo`hostmaster@example.com serial=0

`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=1784494345

Subdomains

mx1.accomplishincreade.tokyo

ns1.accomplishincreade.tokyo

mx2.accomplishincreade.tokyo

ns2.accomplishincreade.tokyo

Same first word

accomplishincreade.tokyo

DNS History

5 records (5 active, 0 former)

●NSns1.accomplishincreade.tokyo2026-04-03 → 2026-07-19 · 2 obs

● 2026-04-03 09:05:38
● 2026-07-19 21:08:22

●NSns2.accomplishincreade.tokyo2026-04-03 → 2026-07-19 · 2 obs

● 2026-04-03 09:05:38
● 2026-07-19 21:08:22

●MXmx1.accomplishincreade.tokyo2026-04-03 → 2026-07-19 · 2 obs

● 2026-04-03 09:05:38
● 2026-07-19 21:08:22

●MXmx2.accomplishincreade.tokyo2026-04-03 → 2026-07-19 · 2 obs

● 2026-04-03 09:05:38
● 2026-07-19 21:08:22

●A122.215.92.1162026-04-03 → 2026-07-19 · 2 obs

● 2026-04-03 09:05:38
● 2026-07-19 21:08:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tokyo	a.gmoregistry.net, k.gmoregistry.net, b.gmoregistry.net, l.gmoregistry.net	7 records
accomplishincreade.tokyo	ns1.accomplishincreade.tokyo, ns2.accomplishincreade.tokyo	2 records

✅ Authoritative Response

Server:122.215.92.116

NS records: ns1.accomplishincreade.tokyo, ns2.accomplishincreade.tokyo

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for accomplishincreade.tokyo (unsigned zone)

⏱️ Timing

Total: 517ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`122.215.92.116`
NS	2	`ns2.accomplishincreade.tokyo, ns1.accomplishincreade.tokyo`
MX	2	`mx1.accomplishincreade.tokyo (pri: 10), mx2.accomplishincreade.tokyo (pri: 20)`
TXT	1	`v=spf1 ~all`
SOA	1	`ns1.accomplishincreade.tokyo hostmaster.`

📌 Glue Records Collected

Total: 9

In-bailiwick: 2 (ns1.accomplishincreade.tokyo, ns2.accomplishincreade.tokyo)

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

Analysis

Hierarchy

accomplishincreade.tokyo serves as the parent of mx1.accomplishincreade.tokyo, ns1.accomplishincreade.tokyo, mx2.accomplishincreade.tokyo and ns2.accomplishincreade.tokyo.

IP Addresses

accomplishincreade.tokyo directs to one IP number, which is 122.215.92.116.

Among the host names that share IP numbers with accomplishincreade.tokyo are 2z7f.com, asstink.com, m.dw8g.com and two others.

Name Servers

accomplishincreade.tokyo is delegated to two name servers: ns1.accomplishincreade.tokyo and ns2.accomplishincreade.tokyo.

ns1.accomplishincreade.tokyo and ns2.accomplishincreade.tokyo both resolve to the same single IP address: 122.215.92.116.

ns1.accomplishincreade.tokyo and ns2.accomplishincreade.tokyo are host names that each point to 122.215.92.116 IP addresses.

Mail Servers

The MX records for accomplishincreade.tokyo point to two mail servers: mx1.accomplishincreade.tokyo and mx2.accomplishincreade.tokyo.

mx1.accomplishincreade.tokyo and mx2.accomplishincreade.tokyo both resolve to the same single IP address: 122.215.92.116.

mx1.accomplishincreade.tokyo and mx2.accomplishincreade.tokyo are host names that each point to 122.215.92.116 IP addresses.

accomplishincreade.tokyo - robtex.com