context safety score
A score of 29/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 'usnssgovcloud.io' mimics US government infrastructure by combining 'us', 'nss' (National Security Systems), 'gov', and 'cloud' into a non-.gov TLD. This pattern is consistent with typosquatting and brand impersonation of official US government domains (which use .gov TLD exclusively). (location: metadata.json: domain=usnssgovcloud.io)
phishing
The domain 'usnssgovcloud.io' uses a .io TLD while incorporating 'gov' and 'us' in the name to deceive users into believing they are visiting a legitimate US government site. This is a classic phishing domain construction targeting users expecting official government services. (location: metadata.json: url=https://usnssgovcloud.io)
social engineering
The domain name structure combines authoritative government-associated terms ('us', 'nss', 'gov', 'cloud') to create a false sense of legitimacy and official authority, a social engineering tactic designed to lower user vigilance and increase trust. (location: metadata.json: domain=usnssgovcloud.io)
malicious redirect
TLS connection failed (connected=false, cert_valid=false) for a domain impersonating government infrastructure. The site may be serving content over an insecure channel or redirecting to a different host, consistent with credential harvesting or malicious redirect infrastructure. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
The combination of government brand impersonation via domain name and failed TLS (no valid certificate) is a high-risk indicator of a credential harvesting site designed to capture login credentials from users who believe they are accessing a legitimate US government portal. (location: metadata.json: domain=usnssgovcloud.io, tls.connected=false)
curl https://api.brin.sh/domain/usnssgovcloud.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
usnssgovcloud.io currently scores 29/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.