context safety score
A score of 43/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
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
A script dynamically injects an external JavaScript file from 'scaredslip.com', an unrecognized third-party domain with no apparent relationship to the site. The script is obfuscated using percent-encoded variable names (decodeURI('a%64%6d%69r%61l')) and uses localStorage manipulation and Google Ad targeting hooks. This pattern is consistent with ad-fraud malware or a supply-chain compromise injecting unauthorized scripts. (location: page-text.txt:1881 / page.html inline script block near bottom of body)
obfuscated code
JavaScript code uses percent-encoded strings (decodeURI('a%64%6d%69r%61l') decodes to 'admiral') combined with obfuscated variable names and indirect localStorage access patterns to evade static detection. The block manipulates Google Ad pubads targeting with data pulled from localStorage under an obfuscated key '%76%34%61%631ei%5a%720'. This level of obfuscation is atypical for legitimate ad code and warrants investigation. (location: page-text.txt:1881 / page.html inline script block)
curl https://api.brin.sh/domain/coloradosun.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
coloradosun.com currently scores 43/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.