🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`hellozcm.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:d3d2^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::6815:3b1d^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.59.29^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.211.210^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`kyle.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c6f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kyle.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c36f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kyle.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:236f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kyle.ns.cloudflare.com`
		A	108.162.195.111^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kyle.ns.cloudflare.com`
		A	162.159.44.111^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kyle.ns.cloudflare.com`
		A	172.64.35.111^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kyle.ns.cloudflare.com`
NS	`pearl.ns.cloudflare.com`
		A	2606:4700:50::a29f:268c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c28c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pearl.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:228c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pearl.ns.cloudflare.com`
		A	108.162.194.140^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	162.159.38.140^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	172.64.34.140^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽²⁰⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁹²⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.59.29, 172.67.211.210
		IPv6 hints	2606:4700:3031::ac43:d3d2, 2606:4700:3035::6815:3b1d
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=3, name=cloudflare-ech.com
SOA	`kyle.ns.cloudflare.com`dns@cloudflare.com serial=2416811990

`dev`

	DNSSEC	🔒 Signed (DS record present)
	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

hellozcm.dev

Similar names

homezllc.com

zollchem.com

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSkyle.ns.cloudflare.com2026-10-06 → 2026-11-07 · 2 obs

● 2026-10-06 19:58:08
● 2026-11-07 14:52:04

●NSpearl.ns.cloudflare.com2026-10-06 → 2026-11-07 · 2 obs

● 2026-10-06 19:58:08
● 2026-11-07 14:52:04

●MXroute1.mx.cloudflare.net2026-10-06 → 2026-11-07 · 2 obs

● 2026-10-06 19:58:08
● 2026-11-07 14:52:04

●MXroute2.mx.cloudflare.net2026-10-06 → 2026-11-07 · 2 obs

● 2026-10-06 19:58:08
● 2026-11-07 14:52:04

●MXroute3.mx.cloudflare.net2026-10-06 → 2026-11-07 · 2 obs

● 2026-10-06 19:58:08
● 2026-11-07 14:52:04

●A104.21.59.292026-10-17 → 2026-11-07 · 2 obs

● 2026-10-17 05:26:10
● 2026-11-07 14:52:04

●A172.67.211.2102026-10-17 → 2026-11-07 · 2 obs

● 2026-10-17 05:26:10
● 2026-11-07 14:52:04

●A2606:4700:3031::ac43:d3d22026-10-17 → 2026-11-07 · 2 obs

● 2026-10-17 05:26:10
● 2026-11-07 14:52:04

●A2606:4700:3035::6815:3b1d2026-10-17 → 2026-11-07 · 2 obs

● 2026-10-17 05:26:10
● 2026-11-07 14:52:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com...	-
hellozcm.dev	kyle.ns.cloudflare.com, pearl.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.38.140

NS records: kyle.ns.cloudflare.com, pearl.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hellozcm.dev (unsigned zone)

⏱️ Timing

Total: 1278ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.59.29, 172.67.211.210`
AAAA	2	`2606:4700:3031::ac43:d3d2, 2606:4700:3035::6815:3b1d`
NS	2	`kyle.ns.cloudflare.com, pearl.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 2), route2.mx.cloudflare.net (pri: 20)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`kyle.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

hellozcm.dev points to the four IP addresses 104.21.59.29, 172.67.211.210, 2606:4700:3031::ac43:d3d2 and 2606:4700:3035::6815:3b1d.

beatosblog.com, www.e-move.com.ua, hotelswithhottubintheroom.com and two other host names share IP numbers with hellozcm.dev.

Name Servers

hellozcm.dev uses two name servers for its delegation: kyle.ns.cloudflare.com and pearl.ns.cloudflare.com.

hellozcm.dev uses the same name servers as several other domains — among them spire-echo.com, otto-markets.com, kathleendcorley.workers.dev and two more.

At least some of hellozcm.dev's name servers are shared with other domains, for example maximove81.workers.dev, diplomacycommunity.org, tbh91tv.cc and two more.

These name servers tend to be deployed in combination with the name servers jule.ns.cloudflare.com and lady.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

Hostname kyle.ns.cloudflare.com directs to 108.162.195.111, 162.159.44.111 and 172.64.35.111 along with 3 other IP addresses.

Hostname pearl.ns.cloudflare.com directs to 108.162.194.140, 162.159.38.140 and 172.64.34.140 along with 3 other IP addresses.

Mail Servers

The MX records for hellozcm.dev list three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

hellozcm.dev has at least partial mail server overlap with other domains such as twikify.xyz, aisafetybcn.org, polybet.uk and two more.

Hostnames that resolve to 6 IP addresses:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.

hellozcm.dev - robtex.com

hellozcm.dev

dev

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`hellozcm.dev`

`dev`