Hostname
claudfront.net
Last fetched
claudfront.net resolves to 104.21.53.116, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. claudfront.net is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:44:38 GMT
- Last seen on a feed
- Wed, 23 Sep 2026 00:57:35 GMT
Nutrition Label
Resolution chain
- 104.21.53.116
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.234.24.211
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.57.117
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.67.212.159
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- privacy service provided by withheld for privacy ehf
- Contact emails
- 08035c63d48e4b7b98c1344570d517b4.protect@withheldforprivacy.com
Subdomains
Mail and authentication
Nameservers
- fattouche.ns.cloudflare.com
- tessa.ns.cloudflare.com
- dns101.registrar-servers.com
- dns102.registrar-servers.com
- ns1.claudfront.net
- ns2.claudfront.net
- a.gtld-servers.net
- b.gtld-servers.net
- c.gtld-servers.net
- d.gtld-servers.net
- e.gtld-servers.net
- f.gtld-servers.net
- g.gtld-servers.net
- h.gtld-servers.net
- i.gtld-servers.net
- j.gtld-servers.net
- k.gtld-servers.net
- l.gtld-servers.net
- m.gtld-servers.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mx.plingest.com
Threat-feed evidence
History
Related pages
Pivot from claudfront.net into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "claudfront.net"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.