🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`slashcommand.dev`

DNSSEC	⚠️ Not signed
A	2001:4860:4802:32::15^{🇺🇸 Google2001:4860::/32}
		PTR	`any-in-2001-4860-4802-32--15.1e100.net`
A	2001:4860:4802:34::15^{🇺🇸 Google2001:4860::/32}
A	2001:4860:4802:36::15^{🇺🇸 Google2001:4860::/32}
A	2001:4860:4802:38::15^{🇺🇸 Google2001:4860::/32}
A	216.239.32.21^{🇺🇸 Google216.239.32.0/24}
A	216.239.34.21^{🇺🇸 Google216.239.34.0/24}
A	216.239.36.21^{🇺🇸 Google216.239.36.0/24}
A	216.239.38.21^{🇺🇸 Google216.239.38.0/24}
NS	`ns-cloud-d1.googledomains.com` ⭐
		A	2001:4860:4802:32::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d1.googledomains.com`
		A	216.239.32.109^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-d1.googledomains.com`
NS	`ns-cloud-d2.googledomains.com`
		A	2001:4860:4802:34::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d2.googledomains.com`
		A	216.239.34.109^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-d2.googledomains.com`
NS	`ns-cloud-d3.googledomains.com`
		A	2001:4860:4802:36::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d3.googledomains.com`
		A	216.239.36.109^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-d3.googledomains.com`
NS	`ns-cloud-d4.googledomains.com`
		A	2001:4860:4802:38::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d4.googledomains.com`
		A	216.239.38.109^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-d4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:2009::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxer-in-f26.1e100.net`
		A	172.217.75.27^{🇺🇸 Google172.217.75.0/24}
			PTR	`yuphxej-in-f27.1e100.net`
MX	`alt1.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	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f26.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4001:c79::1b^{🇺🇸 Google2607:f8b0:4001::/48}
			PTR	`yucbfwv-in-f27.1e100.net`
		A	173.194.42.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yucbfwv-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4003:c4a::1a^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f26.1e100.net`
		A	142.251.96.27^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f27.1e100.net`
TXT	`google-site-verification=ACbpJVM4nsyaWBPeQmYNgycXWi4AKtMuIbYVHER3zrc`
TXT	`v=spf1 include:_spf.firebasemail.com ~all`
TXT	`firebase=mekin-484813`
SOA	`ns-cloud-d1.googledomains.com`cloud-dns-hostmaster@google.com serial=1

`dev`

	DNSSEC	⚠️ Not signed
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

slashcommand.com

slashcommand.dev

slashcommand.app

slashcommand.club

slashcommand.ai

slashcommand.io

Similar names

commandslash.com

Previous names

Next names

DNS History

17 records (17 active, 0 former)

●NSns-cloud-d1.googledomains.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●NSns-cloud-d2.googledomains.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●NSns-cloud-d3.googledomains.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●NSns-cloud-d4.googledomains.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●MXalt1.aspmx.l.google.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●MXalt2.aspmx.l.google.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●MXalt3.aspmx.l.google.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●MXalt4.aspmx.l.google.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●MXaspmx.l.google.com2026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A2001:4860:4802:32::152026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A2001:4860:4802:34::152026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A2001:4860:4802:36::152026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A2001:4860:4802:38::152026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A216.239.32.212026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A216.239.34.212026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A216.239.36.212026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

●A216.239.38.212026-08-31 → 2026-11-05 · 2 obs

● 2026-08-31 02:28:22
● 2026-11-05 21:17:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com...	-
slashcommand.dev	ns-cloud-d4.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com	-

✅ Authoritative Response

Server:216.239.34.109

NS records: ns-cloud-d4.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 2662ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`216.239.32.21, 216.239.36.21...`
AAAA	4	`2001:4860:4802:36::15, 2001:4860:4802:34::15...`
NS	4	`ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	3	`google-site-verification=ACbpJVM4nsyaWBP, firebase=mekin-484813...`
SOA	1	`ns-cloud-d1.googledomains.com cloud-dns-`

Analysis

IP Addresses

With 8 IP addresses in total, slashcommand.dev resolves to 216.239.32.21, 216.239.34.21, 216.239.36.21 and 5 other.

Among the host names that share IP numbers with slashcommand.dev are elementairms.com, baiyuxi.top, sag-pro.com and two others.

Name Servers

The domain slashcommand.dev is delegated to these four name servers: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.

slashcommand.dev has at least partial name server overlap with other domains, such as sailakunikida.com, ctecig.com, paulaarroyometier.com and two others.

ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com all point to exactly two IP numbers each: ns-cloud-d1.googledomains.com → 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com → 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com → 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com → 216.239.38.109 and 2001:4860:4802:38::6d.

Mail Servers

slashcommand.dev is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

slashcommand.dev shares at least some of its mail servers with other domains — for example navi3d.mx, utour.apartments, japan-dining-world.com and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com maps to two IP addresses — 172.217.75.27 and 2607:f8b0:4023:2009::1a.

alt1.aspmx.l.google.com maps to two IP addresses — 172.253.145.27 and 2607:f8b0:4023:3003::1a.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.135.27 and 2607:f8b0:4023:1015::1a.

alt3.aspmx.l.google.com maps to two IP addresses — 173.194.42.27 and 2607:f8b0:4001:c79::1b.

alt4.aspmx.l.google.com maps to two IP addresses — 142.251.96.27 and 2607:f8b0:4003:c4a::1a.