context safety score
A score of 27/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 'ext-twitch.tv' impersonates Twitch (twitch.tv) by prepending 'ext-' to the legitimate brand domain. This is a classic typosquatting/brandjacking pattern designed to deceive users into believing they are visiting the official Twitch platform. (location: domain: ext-twitch.tv)
phishing
The domain 'ext-twitch.tv' is a lookalike of twitch.tv. Combined with TLS failure (connected=false, cert_valid=false), the site is likely a phishing page targeting Twitch users. The inability to establish a valid TLS connection is consistent with a newly registered or poorly configured fraudulent site. (location: domain: ext-twitch.tv, metadata.json tls block)
credential harvesting
A Twitch brand-impersonating domain with no valid TLS certificate is a strong indicator of a credential harvesting operation, targeting Twitch login credentials (username/password, OAuth tokens, or 2FA codes) from users deceived by the lookalike domain. (location: domain: ext-twitch.tv)
malicious redirect
The domain 'ext-twitch.tv' may serve as a redirect intermediary — forwarding victims to a credential-harvesting page or back to the real twitch.tv after capture. The empty page content is consistent with a redirect-only or bot-filtered landing page that serves different content to real users. (location: domain: ext-twitch.tv, page.html (empty))
curl https://api.brin.sh/domain/ext-twitch.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
ext-twitch.tv currently scores 27/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.