mt-cloud.jp - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`mt-cloud.jp`

DNSSEC	⚠️ Not signed
A	85.131.213.74^{🇯🇵 XSERVER-AS85.131.192.0/18 XSERVER Inc.}
		PTR	`sv16693.xserver.jp`
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	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	2607:f8b0:4004:c07::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f26.1e100.net`
		A	2607:f8b0:4004:c07::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f27.1e100.net`
		A	2607:f8b0:4004:c09::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f26.1e100.net`
		A	172.253.62.26^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f26.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f27.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f26.1e100.net`
		A	172.253.115.27^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f27.1e100.net`
		A	172.253.122.26^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f26.1e100.net`
TXT	`v=spf1 +a:sv16693.xserver.jp +a:mt-cloud.jp +mx include:spf.sender.xserver.jp...`
TXT	`google-site-verification=e3ZzEENjTE7xEvVWs_QAY73tgvMBJLJJ1b_YMs6nOXw`
SOA	`ns1.xserver.jp`root@xserver.jp serial=0

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

Same first word

mt-cloud.net

mt-cloud.jp

mt-cloud.com

mt-cloud.de

Similar names

tm-cloud.de

tm-cloud.com

tm-cloud.ru

DNS History

7 records (7 active, 0 former)

●NSns1.xserver.jp2026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

●NSns2.xserver.jp2026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

●NSns3.xserver.jp2026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

●NSns4.xserver.jp2026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

●NSns5.xserver.jp2026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

●MXsmtp.google.com2026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

●A85.131.213.742026-03-22 → 2026-08-15 · 2 obs

● 2026-03-22 22:11:26
● 2026-08-15 13:48:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	g.dns.jp, d.dns.jp, a.dns.jp, b.dns.jp...	-
mt-cloud.jp	ns1.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp...	11 records

✅ Authoritative Response

Server:202.226.36.164

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mt-cloud.jp (unsigned zone)

⏱️ Timing

Total: 993ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`85.131.213.74`
NS	5	`ns1.xserver.jp, ns5.xserver.jp...`
MX	1	`SMTP.GOOGLE.COM (pri: 1)`
TXT	2	`v=spf1 +a:sv16693.xserver.jp +a:mt-cloud, google-site-verification=e3ZzEENjTE7xEvV`
SOA	1	`ns1.xserver.jp root.xserver.jp`

📌 Glue Records Collected

Total: 11

Out-of-bailiwick: 11 (ns5.xserver.jp, ns5.xserver.jp, ns5.xserver.jp...)

Analysis

IP Addresses

mt-cloud.jp resolves to just one IP address, 85.131.213.74.

Two other host names, along with asakusaengei.com, namakaki.net and tokyodoken-minato.jp, also share IP numbers with mt-cloud.jp.

Name Servers

mt-cloud.jp delegates to five name servers: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp and two others.

mt-cloud.jp partially shares its NS delegation with several other domains, including cafe-eikokuya.jp, counter-attraction.jp, lagracia.co.jp and two others.

These name servers are regularly seen alongside ns4.xserver.jp and ns5.xserver.jp as name servers.

Hostnames that map to three IP numbers:

ns1.xserver.jp maps to three IP addresses: 202.226.36.164, 202.226.36.170 and 202.226.36.246.

ns4.xserver.jp maps to three IP addresses: 183.90.224.226, 183.90.224.230 and 202.226.39.247.

ns5.xserver.jp maps to three IP addresses: 157.112.182.218, 157.112.182.220 and 202.226.37.247.

Host names that point to one IP address:

ns2.xserver.jp resolves to the IP address 35.72.43.26.

ns3.xserver.jp resolves to the IP address 202.226.36.247.

Mail Servers

The sole mail server for mt-cloud.jp is smtp.google.com.

Among the domains sharing a mail server setup with mt-cloud.jp are coverplayard.com, mail.buffalosystems.co.uk, samharen.com and two others.

There is at least a partial MX overlap between mt-cloud.jp and other domains, including it2go.mx, bkuic.com, lifebackcoaching.com and two others.

With 9 IP addresses total, smtp.google.com resolves to 172.253.62.26, 172.253.62.27, 172.253.63.26 and 6 others.