context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'clerkprod-cloudflare.net' combines 'clerk' (Clerk.com, an authentication provider) and 'cloudflare' (Cloudflare, a major CDN/security provider) into a single deceptive domain name. This typosquats two well-known brands to appear legitimate, likely targeting developers or AI agents that interact with authentication or infrastructure APIs. (location: domain: clerkprod-cloudflare.net)
phishing
The domain impersonates both Clerk (auth platform) and Cloudflare simultaneously while having TLS connection failure (connected=false, cert_valid=false). A site combining two trusted brand names with no valid TLS is a strong indicator of a phishing or credential harvesting operation targeting developers or automated systems expecting legitimate auth/CDN endpoints. (location: domain: clerkprod-cloudflare.net, metadata.json tls block)
credential harvesting
The combination of 'clerk' (authentication-as-a-service) and 'cloudflare' in the domain strongly suggests targeting of developer credentials, API keys, or authentication tokens. Clerk is specifically an auth provider, making this domain highly likely to be designed to intercept credentials submitted by users or AI agents attempting to authenticate. (location: domain: clerkprod-cloudflare.net)
malicious redirect
TLS is not connected (connected=false) and certificate is invalid (cert_valid=false, san_match=false) despite the domain existing. The site may serve as a redirect intermediary or DNS hijack point rather than a functioning web service, routing traffic to a malicious destination without establishing a direct TLS session with scanners. (location: metadata.json tls block: connected=false, cert_valid=false, san_match=false)
curl https://api.brin.sh/domain/clerkprod-cloudflare.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
clerkprod-cloudflare.net currently scores 36/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.