🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`fdfl.ai`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::ac43:9ad0^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::6815:629^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.6.41^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.154.208^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`kara.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a7b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kara.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c07b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kara.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:207b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kara.ns.cloudflare.com`
		A	108.162.192.123^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kara.ns.cloudflare.com`
		A	172.64.32.123^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kara.ns.cloudflare.com`
		A	173.245.58.123^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kara.ns.cloudflare.com`
NS	`rick.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b8b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c18b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rick.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:218b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rick.ns.cloudflare.com`
		A	108.162.193.139^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	172.64.33.139^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	173.245.59.139^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
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`
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`
TXT	`facebook-domain-verification=u3q1q99eeg5x1ufwt40myejvrdhufw`
TXT	`google-site-verification=znduWri8CzfotxFC_5AHH9lBIJhj2-BdSnzMNEDIgzU`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.6.41, 172.67.154.208
		IPv6 hints	2606:4700:3033::ac43:9ad0, 2606:4700:3034::6815:629
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=66, name=cloudflare-ech.com
SOA	`kara.ns.cloudflare.com`dns@cloudflare.com serial=2411898341

`ai`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.ai` ⭐
	NS	`v0n1.nic.ai`
	NS	`v0n2.nic.ai`
	NS	`v0n3.nic.ai`
	NS	`v2n0.nic.ai`
	NS	`v2n1.nic.ai`
	SOA	`v0n0.nic.ai`hostmaster@donuts.email serial=1786885485

Same first word

fdfl.com

fdfl.ai

Similar names

dlff.org

fldf.de

ffdl.co.uk

dlff.eu

dlff.dk

lfdf.cn

dflf.net

ffdl.mobi

dffl.com.cn

flfd.net

dffl.dk

lffd.org

flfd.org

dffl.com

fldf.be

fdlf.fr

ffdl.cn

ffdl.net

lfdf.fr

fldf.net

ffdl.pro

flfd.com

lffd.com

ffld.cn

dflf.com

ffld.agency

fldf.online

fdlf.org

ffdl.com

fldf.com

lffd.net

fldf.eu

dffl.de

lfdf.life

ldff.cn

flfd.com.cn

dffl.xyz

ffdl.it

ffld.de

ldff.de

ffld.net

fdlf.com

ffld.at

ffdl.de

dlff.de

ffdl.org

dflf.or.kr

lfdf.com

DNS History

9 records (9 active, 0 former)

●NSkara.ns.cloudflare.com2026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●NSrick.ns.cloudflare.com2026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●MXroute1.mx.cloudflare.net2026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●MXroute2.mx.cloudflare.net2026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●MXroute3.mx.cloudflare.net2026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●A104.21.6.412026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●A172.67.154.2082026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●A2606:4700:3033::ac43:9ad02026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

●A2606:4700:3034::6815:6292026-08-13 → 2026-08-16 · 2 obs

● 2026-08-13 00:28:48
● 2026-08-16 13:14:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ai	v0n0.nic.ai, v0n1.nic.ai, v0n2.nic.ai, v0n3.nic.ai...	-
fdfl.ai	kara.ns.cloudflare.com, rick.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.139

NS records: kara.ns.cloudflare.com, rick.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fdfl.ai (unsigned zone)

⏱️ Timing

Total: 494ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.6.41, 172.67.154.208`
AAAA	2	`2606:4700:3033::ac43:9ad0, 2606:4700:3034::6815:629`
NS	2	`kara.ns.cloudflare.com, rick.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 27), route3.mx.cloudflare.net (pri: 79)...`
TXT	3	`facebook-domain-verification=u3q1q99eeg5, google-site-verification=znduWri8CzfotxF...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`kara.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

fdfl.ai resolves to four IP addresses: 104.21.6.41, 172.67.154.208, 2606:4700:3033::ac43:9ad0 and 2606:4700:3034::6815:629.

www.135phpgames.cc, tejerocketri.ink, 161ffff161.com plus two other host names have IP numbers in common with fdfl.ai.

Name Servers

fdfl.ai is delegated to two name servers: kara.ns.cloudflare.com and rick.ns.cloudflare.com.

The name server configuration of fdfl.ai is shared with other domains, for instance turn-games.com, nexgeno.in, razonaconestefa.com and two others.

fdfl.ai partially shares its NS delegation with several other domains, including getinfootball.com, autobuilders.com, jcstoneinc.com and two others.

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

Hosts with 6 IP addresses each:

kara.ns.cloudflare.com resolves to 108.162.192.123, 172.64.32.123, 173.245.58.123 and 3 other IP addresses.

rick.ns.cloudflare.com resolves to 108.162.193.139, 172.64.33.139, 173.245.59.139 and 3 other IP addresses.

Mail Servers

fdfl.ai uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by fdfl.ai are shared with other domains: mynextlisten.com, redage.ru, justicepersonalinjury.com and two others among them.

Hosts with 6 IP addresses each:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.

fdfl.ai - robtex.com

fdfl.ai

ai

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`fdfl.ai`

`ai`