context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
The BridPlugin meta tag contains an oauth_token field with a value encoded in binary (space-separated 8-bit groups): '01110011 01100101 01100011 01110010 01100101 01110100', which decodes to the string 'secret'. Embedding a credential-like token in binary encoding within a meta tag is an obfuscation technique that conceals the value from casual inspection while making it readable to automated parsers or scrapers. (location: page.html line 153: <meta name="BridPlugin" content="site:17402|oauth_token:01110011 01100101 01100011 01110010 01100101 01110100|ver:3.6.5|...">)
hidden content
A <gwmw> element with style="display:none" is present in the page body. This is an injected hidden element (typically from the Grammarly browser extension) and is not part of the site's authored content, but represents a class of hidden DOM node that could be leveraged for concealing content from visual inspection. (location: page.html line 470: <gwmw style="display:none;"></gwmw>)
hidden content
The BridPlugin meta tag exposes internal platform configuration including site ID (17402), user ID (17966), player ID (22787), unit ID (14699), channel ID (18), and multiple feature flags. This information leakage is not dangerous to end users but could be exploited by an adversary or AI agent to understand the site's ad infrastructure and targeting configuration. (location: page.html line 153: <meta name="BridPlugin" content="site:17402|...|user_id:17966|...">)
curl https://api.brin.sh/domain/target-video.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
target-video.com currently scores 49/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.