🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`commandervoodoo.com`

DNSSEC	⚠️ Not signed
A	173.254.111.236
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
MX	`smtp.google.com` ⭐
		A	2a00:1450:4013:c00::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`ei-in-f26.1e100.net`
		A	2a00:1450:4013:c00::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`ei-in-f27.1e100.net`
		A	2a00:1450:4013:c05::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`eg-in-f26.1e100.net`
			PTR	`eg-in-x1a.1e100.net`
		A	2a00:1450:4013:c07::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`el-in-f27.1e100.net`
		A	142.251.31.26^{🇺🇸 Google142.251.31.0/24}
			PTR	`eq-in-f26.1e100.net`
		A	172.217.218.26^{🇺🇸 Google172.217.218.0/24}
			PTR	`en-in-f26.1e100.net`
		A	172.217.218.27^{🇺🇸 Google172.217.218.0/24}
			PTR	`en-in-f27.1e100.net`
		A	172.253.153.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yugrqfv-in-f27.1e100.net`
		A	192.178.156.26^{🇺🇸 Google192.178.156.0/24}
			PTR	`yugrqog-in-f26.1e100.net`
TXT	`v=spf1 +a +mx +ip4:50.87.176.97 +ip4:173.254.111.236 +include:_spf.google.com...`
SOA	`NS1.BLUEHOST.com`root@BLUEHOST.com serial=126040711

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

Same first word

commandervoodoo.com

DNS History

4 records (4 active, 0 former)

●NSns1.bluehost.com2026-09-07 → 2026-11-05 · 2 obs

● 2026-09-07 02:04:12
● 2026-11-05 04:44:12

●NSns2.bluehost.com2026-09-07 → 2026-11-05 · 2 obs

● 2026-09-07 02:04:12
● 2026-11-05 04:44:12

●MXsmtp.google.com2026-09-07 → 2026-11-05 · 2 obs

● 2026-09-07 02:04:12
● 2026-11-05 04:44:12

●A173.254.111.2362026-09-07 → 2026-11-05 · 2 obs

● 2026-09-07 02:04:12
● 2026-11-05 04:44:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net...	-
commandervoodoo.com	ns1.bluehost.com, ns2.bluehost.com	2 records

✅ Authoritative Response

Server:162.159.24.80

NS records: ns1.bluehost.com, ns2.bluehost.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for commandervoodoo.com (unsigned zone)

⏱️ Timing

Total: 1173ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`173.254.111.236`
NS	2	`ns1.bluehost.com, ns2.bluehost.com`
MX	1	`smtp.google.com (pri: 1)`
TXT	1	`v=spf1 +a +mx +ip4:50.87.176.97 +ip4:173`
SOA	1	`NS1.BLUEHOST.com root.BLUEHOST.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)

Analysis

IP Addresses

commandervoodoo.com directs to one IP number, which is 173.254.111.236.

Name Servers

commandervoodoo.com is delegated to two name servers: ns1.bluehost.com and ns2.bluehost.com.

ns1.bluehost.com directs to 162.159.24.80 and ns2.bluehost.com directs to 162.159.25.175; each host name points to exactly one IP number.

Mail Servers

commandervoodoo.com is handled by one mail server, smtp.google.com.

The host name smtp.google.com points to 9 IP numbers: 142.251.31.26, 172.217.218.26, 172.217.218.27 and 6 other.

commandervoodoo.com - robtex.com