🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`security-attack.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:2985^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:a503^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.41.133^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.165.3^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ainsley.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26d3^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2d3^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ainsley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22d3^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ainsley.ns.cloudflare.com`
		A	108.162.194.211^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	162.159.38.211^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	172.64.34.211^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
NS	`leo.ns.cloudflare.com`
		A	2606:4700:58::a29f:2cf1^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leo.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3f1^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`leo.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23f1^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`leo.ns.cloudflare.com`
		A	108.162.195.241^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leo.ns.cloudflare.com`
		A	162.159.44.241^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leo.ns.cloudflare.com`
		A	172.64.35.241^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leo.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.41.133, 172.67.165.3
		IPv6 hints	2606:4700:3031::6815:2985, 2606:4700:3033::ac43:a503
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=254, name=cloudflare-ech.com
SOA	`ainsley.ns.cloudflare.com`dns@cloudflare.com serial=2413199336

`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

security-attack.dev

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NSainsley.ns.cloudflare.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 09:08:24
● 2026-08-29 10:02:02

●NSleo.ns.cloudflare.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 09:08:24
● 2026-08-29 10:02:02

●A104.21.41.1332026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 09:08:24
● 2026-08-29 10:02:02

●A172.67.165.32026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 09:08:24
● 2026-08-29 10:02:02

●A2606:4700:3031::6815:29852026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 09:08:24
● 2026-08-29 10:02:02

●A2606:4700:3033::ac43:a5032026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 09:08:24
● 2026-08-29 10:02:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com...	-
security-attack.dev	leo.ns.cloudflare.com, ainsley.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.35.241

NS records: leo.ns.cloudflare.com, ainsley.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for security-attack.dev (unsigned zone)

⏱️ Timing

Total: 1524ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.165.3, 104.21.41.133`
AAAA	2	`2606:4700:3033::ac43:a503, 2606:4700:3031::6815:2985`
NS	2	`ainsley.ns.cloudflare.com, leo.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ainsley.ns.cloudflare.com dns.cloudflare`

Analysis

IP Addresses

security-attack.dev points to the four IP addresses 104.21.41.133, 172.67.165.3, 2606:4700:3031::6815:2985 and 2606:4700:3033::ac43:a503.

reeshs.com, fundlyable.biz, adbrains.dk and two other host names share IP numbers with security-attack.dev.

Name Servers

security-attack.dev is served by two delegated name servers, ainsley.ns.cloudflare.com and leo.ns.cloudflare.com.

security-attack.dev uses the same name servers as several other domains — among them yxt2005.com, g2g111s.com, archipelago-artworks.pro and two more.

At least some of security-attack.dev's name servers are shared with other domains, for example gotinyspace.com, zyrencloud.xyz, redtierunnercom.pages.dev and two more.

These name servers tend to be used in conjunction with the name servers alfred.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

ainsley.ns.cloudflare.com carries IP addresses 108.162.194.211, 162.159.38.211 and 172.64.34.211, with 3 other addresses beyond those.

leo.ns.cloudflare.com carries IP addresses 108.162.195.241, 162.159.44.241 and 172.64.35.241, with 3 other addresses beyond those.

security-attack.dev - robtex.com