🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`zerodeploy.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:4759^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:aa4c^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.71.89^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.170.76^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`beau.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b49^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`beau.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c149^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`beau.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2149^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`beau.ns.cloudflare.com`
		A	108.162.193.73^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`beau.ns.cloudflare.com`
		A	172.64.33.73^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`beau.ns.cloudflare.com`
		A	173.245.59.73^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`beau.ns.cloudflare.com`
NS	`jewel.ns.cloudflare.com`
		A	2606:4700:50::a29f:26ab^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jewel.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2ab^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jewel.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22ab^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jewel.ns.cloudflare.com`
		A	108.162.194.171^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jewel.ns.cloudflare.com`
		A	162.159.38.171^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jewel.ns.cloudflare.com`
		A	172.64.34.171^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jewel.ns.cloudflare.com`
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`
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	`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`
TXT	`google-site-verification=jUT2WhG-iEeRXerW-Y935kMj2nMq2MOZD9n2vhLqd8A`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.71.89, 172.67.170.76
		IPv6 hints	2606:4700:3032::6815:4759, 2606:4700:3033::ac43:aa4c
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=75, name=cloudflare-ech.com
SOA	`beau.ns.cloudflare.com`dns@cloudflare.com serial=2413076154

`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

zerodeploy.app

zerodeploy.dev

zerodeploy.nl

Similar names

deployzero.xyz

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSbeau.ns.cloudflare.com2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●NSjewel.ns.cloudflare.com2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●MXroute1.mx.cloudflare.net2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●MXroute2.mx.cloudflare.net2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●MXroute3.mx.cloudflare.net2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●A104.21.71.892026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●A172.67.170.762026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●A2606:4700:3032::6815:47592026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

●A2606:4700:3033::ac43:aa4c2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 08:16:54
● 2026-08-30 01:25:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com...	-
zerodeploy.dev	beau.ns.cloudflare.com, jewel.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.38.171

NS records: beau.ns.cloudflare.com, jewel.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for zerodeploy.dev (unsigned zone)

⏱️ Timing

Total: 715ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.71.89, 172.67.170.76`
AAAA	2	`2606:4700:3032::6815:4759, 2606:4700:3033::ac43:aa4c`
NS	2	`beau.ns.cloudflare.com, jewel.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 28), route2.mx.cloudflare.net (pri: 43)...`
TXT	2	`google-site-verification=jUT2WhG-iEeRXer, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`beau.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

zerodeploy.dev points to the four IP addresses 104.21.71.89, 172.67.170.76, 2606:4700:3032::6815:4759 and 2606:4700:3033::ac43:aa4c.

Among the host names that share IP numbers with zerodeploy.dev are renatahungaro.com.br, texwipe.com, www.nuevohabitat.com.co and two others.

Name Servers

zerodeploy.dev uses two name servers for its delegation: beau.ns.cloudflare.com and jewel.ns.cloudflare.com.

zerodeploy.dev has the same name server delegation as a number of other domains, such as teksisboya.com.tr, afsagrup.com.tr, ajansumb.com.tr and two more.

The name servers of zerodeploy.dev overlap at least partially with those of other domains — among them ewapuz.com, oat606606oat.workers.dev, maildelivery365.net and two more.

These name servers commonly appear alongside the name servers aspen.ns.cloudflare.com and aida.ns.cloudflare.com.

Host names resolving to 6 IP numbers:

Hostname beau.ns.cloudflare.com directs to 108.162.193.73, 172.64.33.73 and 173.245.59.73 along with 3 other IP addresses.

Hostname jewel.ns.cloudflare.com directs to 108.162.194.171, 162.159.38.171 and 172.64.34.171 along with 3 other IP addresses.

Mail Servers

Mail for zerodeploy.dev is routed through three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

zerodeploy.dev shares at least some of its mail servers with other domains — for example ivorywordharbor.com, horizon-web.net, cmdpr.dev and two more.

Host names resolving to 6 IP numbers:

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.

zerodeploy.dev - robtex.com

zerodeploy.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

`zerodeploy.dev`

`dev`