context safety score
A score of 48/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 'alienvault.cloud' impersonates AlienVault, a well-known cybersecurity brand (OTX threat intelligence platform owned by AT&T Cybersecurity). The use of a .cloud TLD instead of the legitimate .com domain is a common brand-squatting tactic targeting security professionals and organizations. (location: domain: alienvault.cloud)
phishing
TLS connection failed (connected=false, cert_valid=false) on a domain impersonating a cybersecurity brand. A site masquerading as AlienVault with no valid TLS certificate is consistent with a phishing infrastructure setup, possibly used to harvest credentials from security researchers or IT professionals expecting the legitimate AlienVault OTX portal. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
The combination of brand impersonation of AlienVault (a platform requiring user login) and invalid TLS suggests the site may be designed to harvest credentials from users who believe they are logging into the legitimate AlienVault OTX threat intelligence platform. (location: domain: alienvault.cloud, metadata.json tls block)
curl https://api.brin.sh/domain/alienvault.cloudCommon questions teams ask before deciding whether to use this domain in agent workflows.
alienvault.cloud currently scores 48/100 with a suspicious verdict and medium 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.