`lexustokyo.jp`

DNSSEC	⚠️ Not signed
A	104.87.193.121^{🇯🇵 Akamai104.87.192.0/21 Technologies}
		PTR	`a104-87-193-121.deploy.static.akamaitechnologies.com`
NS	`majesta.tns.ne.jp` ⭐
		A	210.175.129.70^{🇯🇵 D-CRUISENET210.175.128.0/22 TS}
			PTR	`majesta.tns.ne.jp`
NS	`a1-238.akam.net`
		A	2600:1401:2::ee^{🇺🇸 Akamai2600:1401:2::/48 Technologies}
			PTR	`a1-238.akam.net`
			PTR	`ns1-238.akam.net`
		A	193.108.91.238^{🇳🇱 Akamai193.108.91.0/24 Technologies}
			PTR	`a1-238.akam.net`
			PTR	`ns1-238.akam.net`
NS	`a11-65.akam.net`
		A	2600:1480:1::41^{🇺🇸 Akamai2600:1480:1::/48 Technologies}
			PTR	`a11-65.akam.net`
			PTR	`ns4-65.akam.net`
		A	84.53.139.65^{🇳🇱 Akamai84.53.139.0/24 Technologies}
			PTR	`a11-65.akam.net`
			PTR	`ns4-65.akam.net`
NS	`a2-66.akam.net`
		A	2600:1480:7000::42^{🇺🇸 Akamai2600:1480:7000::/48 Technologies}
			PTR	`a2-66.akam.net`
		A	95.100.174.66^{🇳🇱 Akamai95.100.174.0/24 Technologies}
			PTR	`a2-66.akam.net`
NS	`a26-67.akam.net`
		A	2600:1480:b800::43^{🇺🇸 Akamai2600:1480:b800::/48 Technologies}
			PTR	`a26-67.akam.net`
		A	23.74.25.67^{🇺🇸 Akamai23.74.25.0/24 Technologies}
			PTR	`a26-67.akam.net`
NS	`a5-64.akam.net`
		A	2600:1480:b000::40^{🇺🇸 Akamai2600:1480:b000::/48 Technologies}
			PTR	`a5-64.akam.net`
			PTR	`ns6-64.akam.net`
		A	95.100.168.64^{🇳🇱 Akamai95.100.168.0/24 Technologies}
			PTR	`a5-64.akam.net`
			PTR	`ns6-64.akam.net`
NS	`a8-65.akam.net`
		A	2600:1403:a::41^{🇺🇸 Akamai2600:1403:a::/48 Technologies}
			PTR	`a8-65.akam.net`
		A	2.16.40.65^{🇳🇱 Akamai2.16.40.0/24 Technologies}
			PTR	`a8-65.akam.net`
NS	`royal.tns.ne.jp`
		A	210.175.128.35^{🇯🇵 D-CRUISENET210.175.128.0/22 TS}
			PTR	`royal.tns.ne.jp`
MX	`gw6221.fortimail.com` ⭐
		A	173.243.136.221^{🇨🇦 FORTINET173.243.136.0/24 Fortinet Inc.}
			PTR	`gw6221.fortimail.com`
MX	`lexustokyo-jp.mail.protection.outlook.com`⁽²⁰⁾
		A	2a01:111:f403:cc1a::1^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::2^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00302.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::3^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00203.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1f::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
		A	52.101.124.0^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	52.101.124.5^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tyvp286cu00305.inbound.protection.outlook.com`
		A	52.101.157.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os0p286cu01203.inbound.protection.outlook.com`
		A	52.101.157.40^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
TXT	`google-site-verification=C8udagcAFcsZfP8CQ6sSl_DGEKbxSeAs5TL9FSLC2pk`
TXT	`_globalsign-domain-verification=HiDJWIw9PSZ7UBYo3lTCzJQRvF7HwCAoV2Ij9afNL7`
TXT	`v=spf1 include:willap.jp include:spf.protection.outlook.com include:spf-bma.m...`
TXT	`MS=ms35073546`
TXT	`google-site-verification=DxQ2X8i5Lgrcjm7wvlT5RtrLeQrIMIry176FNmo5NWM`
SOA	`majesta.tns.ne.jp`postmaster@dci.ad.jp serial=1783921263

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

Same first word

lexustokyo.jp

DNS History

15 records (11 active, 4 former)

●NSa1-238.akam.net2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●NSa11-65.akam.net2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●NSa2-66.akam.net2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●NSa26-67.akam.net2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●NSa5-64.akam.net2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●NSa8-65.akam.net2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●NSmajesta.tns.ne.jp2018-05-12 → 2026-07-13 · 2 obs

● 2018-05-12 15:40:58
● 2026-07-13 07:10:02

●NSroyal.tns.ne.jp2018-05-12 → 2026-07-13 · 2 obs

● 2018-05-12 15:40:58
● 2026-07-13 07:10:02

●MXgw6221.fortimail.com2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

●MXlexustokyo-jp.mail.protection.outlook.com2026-03-24 → 2026-07-13 · 3 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-07-13 07:10:02

○MXmx-box01.demail2.d-cruise.jp2018-05-12 → 2018-05-12 · 3 obs

● 2018-05-12 15:40:58
○ 2026-03-24 09:13:38
○ 2026-07-13 07:10:02

○MXmx-box02.demail2.d-cruise.jp2018-05-12 → 2018-05-12 · 3 obs

● 2018-05-12 15:40:58
○ 2026-03-24 09:13:38
○ 2026-07-13 07:10:02

○A104.119.245.1822026-04-08 → 2026-06-13 · 5 obs

○ 2026-04-06 17:37:58
● 2026-04-08 23:21:52
● 2026-06-13 03:31:48
○ 2026-07-08 13:22:10
○ 2026-07-13 07:10:02

○A104.71.146.222018-05-12 → 2018-05-12 · 3 obs

● 2018-05-12 15:40:58
○ 2026-03-24 09:13:38
○ 2026-07-13 07:10:02

●A104.87.193.1212026-03-24 → 2026-07-13 · 7 obs

○ 2018-05-12 15:40:58
● 2026-03-24 09:13:38
● 2026-04-06 17:37:58
○ 2026-04-08 23:21:52
○ 2026-06-13 03:31:48
● 2026-07-08 13:22:10
● 2026-07-13 07:10:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp...	-
lexustokyo.jp	royal.tns.ne.jp, a1-238.akam.net, a11-65.akam.net, a26-67.akam.net...	2 records

✅ Authoritative Response

Server:95.100.174.66

NS records: royal.tns.ne.jp, a1-238.akam.net, a11-65.akam.net, a26-67.akam.net, majesta.tns.ne.jp, a2-66.akam.net, a5-64.akam.net, a8-65.akam.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lexustokyo.jp (unsigned zone)

⏱️ Timing

Total: 1264ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.87.193.121`
NS	8	`a5-64.akam.net, a11-65.akam.net...`
MX	2	`gw6221.fortimail.com (pri: 10), lexustokyo-jp.mail.protection.outlook.co`
TXT	5	`_globalsign-domain-verification=HiDJWIw9, MS=ms35073546...`
SOA	1	`majesta.tns.ne.jp postmaster.dci.ad.jp`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (royal.tns.ne.jp, majesta.tns.ne.jp)

Analysis

IP Addresses

lexustokyo.jp has exactly one IP address — 104.87.193.121.

a104-87-193-121.deploy.static.akamaitechnologies.com, c-shinosaka.jp and n-shinosaka.jp are examples of other host names that share IP numbers with lexustokyo.jp.

Name Servers

DNS for lexustokyo.jp is handled by 8 name servers: a1-238.akam.net, a11-65.akam.net, a2-66.akam.net and 5 others.

lexustokyo.jp partially shares its NS delegation with several other domains, including burtongroup.info, 232.8.141.in-addr.arpa, insearch-online.com and two others.

In DNS configurations, these name servers often share authority with a5-64.akam.net, a8-65.akam.net, a26-67.akam.net and 3 other name servers.

Host names pointing to two IP addresses:

a1-238.akam.net has two IP addresses: 193.108.91.238 and 2600:1401:2::ee.

a11-65.akam.net has two IP addresses: 84.53.139.65 and 2600:1480:1::41.

a2-66.akam.net has two IP addresses: 95.100.174.66 and 2600:1480:7000::42.

a26-67.akam.net has two IP addresses: 23.74.25.67 and 2600:1480:b800::43.

a5-64.akam.net has two IP addresses: 95.100.168.64 and 2600:1480:b000::40.

a8-65.akam.net has two IP addresses: 2.16.40.65 and 2600:1403:a::41.

Host names resolving to a single IP address:

majesta.tns.ne.jp directs to 210.175.129.70.

royal.tns.ne.jp directs to 210.175.128.35.

Mail Servers

lexustokyo.jp uses two mail servers, gw6221.fortimail.com and lexustokyo-jp.mail.protection.outlook.com.

At least some of the mail servers used by lexustokyo.jp are shared with other domains: shigatoyota.co.jp, c-nagoya.co.jp, gifutoyota.co.jp and two others among them.

The mail servers alt1.aspmx.l.google.com and alt2.aspmx.l.google.com regularly co-occur with these mail servers.

Hosts with 8 IP addresses each:

lexustokyo-jp.mail.protection.outlook.com has IP addresses 52.101.124.0, 52.101.124.5 and 52.101.157.11, plus 5 other.

Host names resolving to a single IP address:

gw6221.fortimail.com directs to 173.243.136.221.

lexustokyo.jp - robtex.com

lexustokyo.jp

jp

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`lexustokyo.jp`

`jp`