🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`codeanalyzerme.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:b199^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::6815:2b5f^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.43.95^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.177.153^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`blakely.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2660^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c260^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`blakely.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2260^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`blakely.ns.cloudflare.com`
		A	108.162.194.96^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
		A	162.159.38.96^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
		A	172.64.34.96^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
NS	`kaiser.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c09^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kaiser.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c309^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kaiser.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2309^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kaiser.ns.cloudflare.com`
		A	108.162.195.9^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kaiser.ns.cloudflare.com`
		A	162.159.44.9^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kaiser.ns.cloudflare.com`
		A	172.64.35.9^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kaiser.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.43.95, 172.67.177.153
		IPv6 hints	2606:4700:3030::ac43:b199, 2606:4700:3033::6815:2b5f
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=138, name=cloudflare-ech.com
SOA	`blakely.ns.cloudflare.com`dns@cloudflare.com serial=2415565695

`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

codeanalyzerme.dev

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NSblakely.ns.cloudflare.com2026-09-24 → 2026-09-30 · 2 obs

● 2026-09-24 11:01:16
● 2026-09-30 13:49:02

●NSkaiser.ns.cloudflare.com2026-09-24 → 2026-09-30 · 2 obs

● 2026-09-24 11:01:16
● 2026-09-30 13:49:02

●A104.21.43.952026-09-24 → 2026-09-30 · 2 obs

● 2026-09-24 11:01:16
● 2026-09-30 13:49:02

●A172.67.177.1532026-09-24 → 2026-09-30 · 2 obs

● 2026-09-24 11:01:16
● 2026-09-30 13:49:02

●A2606:4700:3030::ac43:b1992026-09-24 → 2026-09-30 · 2 obs

● 2026-09-24 11:01:16
● 2026-09-30 13:49:02

●A2606:4700:3033::6815:2b5f2026-09-24 → 2026-09-30 · 2 obs

● 2026-09-24 11:01:16
● 2026-09-30 13:49:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
codeanalyzerme.dev	blakely.ns.cloudflare.com, kaiser.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.34.96

NS records: blakely.ns.cloudflare.com, kaiser.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for codeanalyzerme.dev (unsigned zone)

⏱️ Timing

Total: 1011ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.177.153, 104.21.43.95`
AAAA	2	`2606:4700:3030::ac43:b199, 2606:4700:3033::6815:2b5f`
NS	2	`blakely.ns.cloudflare.com, kaiser.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`blakely.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)

Analysis

IP Addresses

codeanalyzerme.dev has four IP addresses: 104.21.43.95, 172.67.177.153, 2606:4700:3030::ac43:b199 and 2606:4700:3033::6815:2b5f.

mixxcenter.online, sefa-pa.site, brjogalogin.com plus two other host names have IP numbers in common with codeanalyzerme.dev.

Name Servers

The NS records for codeanalyzerme.dev delegate to blakely.ns.cloudflare.com and kaiser.ns.cloudflare.com.

The name server configuration of codeanalyzerme.dev is shared with other domains, for instance bettillt-turkey.com, pzeng-wh.workers.dev, hghuyao123.workers.dev and two others.

codeanalyzerme.dev shares at least some of its name servers with other domains, including runcarousel.help, xem-consuldigital.com, workspace-flowcore.click and two others.

These name servers are frequently seen alongside the name servers adele.ns.cloudflare.com, piper.ns.cloudflare.com, toby.ns.cloudflare.com and kobe.ns.cloudflare.com.

Hosts with 6 IP addresses each:

blakely.ns.cloudflare.com maps to 108.162.194.96, 162.159.38.96, 172.64.34.96 and 3 additional IP addresses.

kaiser.ns.cloudflare.com maps to 108.162.195.9, 162.159.44.9, 172.64.35.9 and 3 additional IP addresses.

codeanalyzerme.dev - robtex.com