`rise-aichi.com`

DNSSEC	⚠️ Not signed
A	34.111.141.225^{🇺🇸 Google34.108.0.0/14}
		PTR	`225.141.111.34.bc.googleusercontent.com`
NS	`ns1.xserver.jp` ⭐
		A	202.226.36.164^{🇯🇵 XSERVER-AS202.226.36.0/22 XSERVER Inc.}
		A	202.226.36.170^{🇯🇵 XSERVER-AS202.226.36.0/22 XSERVER Inc.}
		A	202.226.36.246^{🇯🇵 XSERVER-AS202.226.36.0/22 XSERVER Inc.}
			PTR	`ns1.xserver.jp`
NS	`ns2.xserver.jp`
		A	35.72.43.26^{🇯🇵 Amazon35.72.0.0/13 EC2 NRT prefix}
			PTR	`ns2.xserver.jp`
NS	`ns3.xserver.jp`
		A	202.226.36.247^{🇯🇵 XSERVER-AS202.226.36.0/22 XSERVER Inc.}
			PTR	`ns3.xserver.jp`
NS	`ns4.xserver.jp`
		A	183.90.224.226^{🇯🇵 XSERVER-AS183.90.224.0/20 XSERVER Inc.}
		A	183.90.224.230^{🇯🇵 XSERVER-AS183.90.224.0/20 XSERVER Inc.}
		A	202.226.39.247^{🇯🇵 XSERVER-AS202.226.36.0/22 XSERVER Inc.}
			PTR	`ns4.xserver.jp`
NS	`ns5.xserver.jp`
		A	157.112.182.218^{🇯🇵 XSERVER-AS157.112.176.0/21 XSERVER Inc.}
		A	157.112.182.220^{🇯🇵 XSERVER-AS157.112.176.0/21 XSERVER Inc.}
		A	202.226.37.247^{🇯🇵 XSERVER-AS202.226.36.0/22 XSERVER Inc.}
			PTR	`ns5.xserver.jp`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:3003::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f26.1e100.net`
		A	172.253.145.27^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4001:c70::1b^{🇺🇸 Google2607:f8b0:4001::/48}
			PTR	`yucbful-in-f27.1e100.net`
		A	192.178.209.26^{🇺🇸 Google192.178.209.0/24}
			PTR	`yucbful-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`google-site-verification=vTB-AN0FtrdPnZ-Ld8Vq_vLGOd3YBEioiUl8Aa0GQZg`
SOA	`ns1.xserver.jp`root@xserver.jp serial=0

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

Same first word

rise-aichi.com

DNS History

11 records (11 active, 0 former)

●NSns1.xserver.jp2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●NSns2.xserver.jp2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●NSns3.xserver.jp2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●NSns4.xserver.jp2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●NSns5.xserver.jp2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●MXalt1.aspmx.l.google.com2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●MXalt2.aspmx.l.google.com2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●MXalt3.aspmx.l.google.com2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●MXalt4.aspmx.l.google.com2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●MXaspmx.l.google.com2026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

●A34.111.141.2252026-04-24 → 2026-05-01 · 2 obs

● 2026-04-24 21:57:18
● 2026-05-01 23:10:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net...	-
rise-aichi.com	ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp...	-

✅ Authoritative Response

Server:157.112.182.218

NS records: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rise-aichi.com (unsigned zone)

⏱️ Timing

Total: 1242ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`34.111.141.225`
NS	5	`ns4.xserver.jp, ns2.xserver.jp...`
MX	5	`ALT1.ASPMX.L.GOOGLE.com (pri: 5), ALT2.ASPMX.L.GOOGLE.com (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com ~all, google-site-verification=vTB-AN0FtrdPnZ-`
SOA	1	`ns1.xserver.jp root.xserver.jp`

Analysis

IP Addresses

rise-aichi.com resolves to one IP number: 34.111.141.225.

Other host names, for instance dxtrl.com, digima-inc.com, budou-nashi.com, hth-team.com and savemedical.co.jp share IP numbers with rise-aichi.com.

Name Servers

rise-aichi.com is delegated to five name servers: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp and ns5.xserver.jp.

rise-aichi.com at least partially shares name servers with other domains, including farst-exp.com, mo5724.com, wakohmarine.com, sim-mvno.xyz and kumaben.com.