🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`securewithash.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:c25b^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3031::6815:247d^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.36.125^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.194.91^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`denver.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2cc4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3c4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`denver.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23c4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`denver.ns.cloudflare.com`
		A	108.162.195.196^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	162.159.44.196^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	172.64.35.196^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
NS	`melissa.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ac7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0c7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`melissa.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20c7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`melissa.ns.cloudflare.com`
		A	108.162.192.199^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
		A	172.64.32.199^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
		A	173.245.58.199^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.36.125, 172.67.194.91
		IPv6 hints	2606:4700:3030::ac43:c25b, 2606:4700:3031::6815:247d
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=54, name=cloudflare-ech.com
SOA	`denver.ns.cloudflare.com`dns@cloudflare.com serial=2418885655

`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

⚠️ On DNS blocklist: tif, tif.medium
🔒 HSTS Preload (+subdomains)

Same first word

securewithash.dev

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NSdenver.ns.cloudflare.com2026-10-27 → 2026-11-10 · 2 obs

● 2026-10-27 04:44:16
● 2026-11-10 23:36:02

●NSmelissa.ns.cloudflare.com2026-10-27 → 2026-11-10 · 2 obs

● 2026-10-27 04:44:16
● 2026-11-10 23:36:02

●A104.21.36.1252026-11-10 → 2026-11-10 · 2 obs

● 2026-11-10 20:58:38
● 2026-11-10 23:36:02

●A172.67.194.912026-11-10 → 2026-11-10 · 2 obs

● 2026-11-10 20:58:38
● 2026-11-10 23:36:02

●A2606:4700:3030::ac43:c25b2026-11-10 → 2026-11-10 · 2 obs

● 2026-11-10 20:58:38
● 2026-11-10 23:36:02

●A2606:4700:3031::6815:247d2026-11-10 → 2026-11-10 · 2 obs

● 2026-11-10 20:58:38
● 2026-11-10 23:36:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	-
securewithash.dev	melissa.ns.cloudflare.com, denver.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.199

NS records: melissa.ns.cloudflare.com, denver.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 626ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.36.125, 172.67.194.91`
AAAA	2	`2606:4700:3030::ac43:c25b, 2606:4700:3031::6815:247d`
NS	2	`denver.ns.cloudflare.com, melissa.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`denver.ns.cloudflare.com dns.cloudflare.`

Analysis

IP Addresses

securewithash.dev directs to four IP numbers, which are 104.21.36.125, 172.67.194.91, 2606:4700:3030::ac43:c25b and 2606:4700:3031::6815:247d.

mydepositletter.com, 10dollardepositcasinos.org, 2280455.xyz plus two other host names have IP numbers in common with securewithash.dev.

Name Servers

securewithash.dev uses two name servers for its delegation: denver.ns.cloudflare.com and melissa.ns.cloudflare.com.

The name server configuration of securewithash.dev is shared with other domains, for instance ekajaya-group.com, kaypachawellnessplace.com, consciencianutricional.com and two others.

There is at least partial name server overlap between securewithash.dev and other domains — vulnat.com, shadowrionfall.info, durovterrorist.com and two more among them.

These name servers tend to appear in combination with the name servers ajay.ns.cloudflare.com, lily.ns.cloudflare.com, devin.ns.cloudflare.com and jill.ns.cloudflare.com.

Hosts with 6 IP addresses each:

Hostname denver.ns.cloudflare.com directs to 108.162.195.196, 162.159.44.196 and 172.64.35.196 along with 3 other IP addresses.

Hostname melissa.ns.cloudflare.com directs to 108.162.192.199, 172.64.32.199 and 173.245.58.199 along with 3 other IP addresses.

securewithash.dev - robtex.com