Skip to content

Hostname

clientcaf.info

Last fetched

clientcaf.info resolves to 104.219.250.37, announced in 104.219.250.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. clientcaf.info is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Tue, 22 Sep 2026 23:26:40 GMT

Nutrition Label

WHISPER CANON · clientcaf.infoRouting diversity3.0/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint9.2/10canon.whisper.security/host/clientcaf.info

Resolution chain

IPv6 resolution

No AAAA record for clientcaf.info is recorded in WhisperGraph.

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Contact emails
50f9cf88b4364fb787854845ee4a1390.protect@whoisguard.com, f62c7e4898ac430488c379d241a8142f.protect@whoisguard.com, 4bd8c7f70ddf46f9bc58d497184ac1ce.protect@withheldforprivacy.com

Subdomains

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
  • a0.info.afilias-nst.info
  • a2.info.afilias-nst.info
  • c0.info.afilias-nst.info
  • 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
  • b0.info.afilias-nst.org
  • b2.info.afilias-nst.org
  • d0.info.afilias-nst.org
  • ns2.lander.d.parity.domains
  • ns1.lander.d.parity.domains

MX records

  • mail.clientcaf.info

Threat-feed evidence

History

Related pages

Pivot from clientcaf.info 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: "clientcaf.info"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.