🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`fluidattacks.dev`

DNSSEC	🔒 Signed (DS record present)
A	2606:4700:3031::6815:36d2^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:8e17^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.54.210^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.142.23^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`bart.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b47^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bart.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c147^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`bart.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2147^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`bart.ns.cloudflare.com`
		A	108.162.193.71^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bart.ns.cloudflare.com`
		A	172.64.33.71^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bart.ns.cloudflare.com`
		A	173.245.59.71^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bart.ns.cloudflare.com`
NS	`lucy.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a85^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lucy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c085^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lucy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2085^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lucy.ns.cloudflare.com`
		A	108.162.192.133^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lucy.ns.cloudflare.com`
		A	172.64.32.133^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lucy.ns.cloudflare.com`
		A	173.245.58.133^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lucy.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f26.1e100.net`
		A	172.253.115.26^{🇺🇸 Google172.253.115.0/24}
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=O1DzXi3E6LIG3nOgpYkkLDU6rELFVMDoO-HPYllLXPw`
TXT	`v=spf1 include:_spf.google.com -all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.54.210, 172.67.142.23
		IPv6 hints	2606:4700:3031::6815:36d2, 2606:4700:3034::ac43:8e17
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=152, name=cloudflare-ech.com
SOA	`bart.ns.cloudflare.com`dns@cloudflare.com serial=2419981448

`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

Previous names

Next names

DNS History

11 records (11 active, 0 former)

●NSbart.ns.cloudflare.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●NSlucy.ns.cloudflare.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●MXalt1.aspmx.l.google.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●MXalt2.aspmx.l.google.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●MXalt3.aspmx.l.google.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●MXalt4.aspmx.l.google.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●MXaspmx.l.google.com2026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●A104.21.54.2102026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●A172.67.142.232026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●A2606:4700:3031::6815:36d22026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

●A2606:4700:3034::ac43:8e172026-09-22 → 2026-11-14 · 2 obs

● 2026-09-22 18:38:30
● 2026-11-14 00:14:56

🔍 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
fluidattacks.dev	bart.ns.cloudflare.com, lucy.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.71

NS records: bart.ns.cloudflare.com, lucy.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: 476ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.142.23, 104.21.54.210`
AAAA	2	`2606:4700:3031::6815:36d2, 2606:4700:3034::ac43:8e17`
NS	2	`bart.ns.cloudflare.com, lucy.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=O1DzXi3E6LIG3nO, v=spf1 include:_spf.google.com -all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`bart.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 10

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

Analysis

IP Addresses

fluidattacks.dev has four IP addresses: 104.21.54.210, 172.67.142.23, 2606:4700:3031::6815:36d2 and 2606:4700:3034::ac43:8e17.

Two other host names, along with bteamarms.com, urbanizab2b.eu.org and 2346555.com, also share IP numbers with fluidattacks.dev.

Name Servers

fluidattacks.dev uses two name servers for its delegation: bart.ns.cloudflare.com and lucy.ns.cloudflare.com.

fluidattacks.dev shares its NS records with other domains, for example rpbigbag.pages.dev, morganandtim.co.uk, fg14.pages.dev and two others.

fluidattacks.dev partially shares its NS delegation with several other domains, including intensivelivesurgery.com, cemei.mx, folhadoaco.com.br and two others.

These name servers often co-occur with the name servers maria.ns.cloudflare.com.

DNS names with 6 IP addresses:

Hostname bart.ns.cloudflare.com directs to 108.162.193.71, 172.64.33.71 and 173.245.59.71 along with 3 other IP addresses.

Hostname lucy.ns.cloudflare.com directs to 108.162.192.133, 172.64.32.133 and 173.245.58.133 along with 3 other IP addresses.

Mail Servers

Mail for fluidattacks.dev is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between fluidattacks.dev and other domains, including waldenwindowwashing.com, allinmotionclub.com, kloudserv.us and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 172.253.115.26 and 2607:f8b0:4004:c1f::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.