context safety score
A score of 44/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
brand impersonation
Page is served at cashstar.com but the HTML <title> tag reads 'blackhawknetwork.com'. CashStar is a gift-card platform owned by Blackhawk Network, but presenting a different brand name in the title while the URL shows cashstar.com is a classic indicator of brand impersonation or domain squatting — a visitor (or AI agent) resolving cashstar.com would be told by the page metadata that they are on blackhawknetwork.com. (location: page.html:<title> tag, line 1)
malicious redirect
The entire page body is a bot-detection/CAPTCHA gate that loads an external script from 'ct.captcha-delivery.com' and phones home to 'geo.captcha-delivery.com'. The page contains no legitimate content and immediately redirects non-JS or detected-bot traffic. This pattern is used to serve different content to human users vs. automated scanners, a technique commonly employed to hide phishing or malicious payloads from security crawlers while displaying them to real victims. (location: page.html: <script src='https://ct.captcha-delivery.com/c.js'>, line 1)
hidden content
The visible page content is entirely a CAPTCHA/JS-gate stub ('Please enable JS and disable any ad blocker'). All real page content is hidden behind client-side JavaScript execution gated by an external bot-detection service (captcha-delivery.com / DataDome). This means the actual page content served to human users is completely concealed from static analysis, a technique frequently used to cloak phishing, credential-harvesting, or other malicious content from automated scanners. (location: page.html: full body, line 1)
obfuscated code
The inline script contains a DataDome bot-detection payload with encoded fields: a base64-encoded 'cid', a hex hash 'hsh', and a long hex string 'e' that appear to be session/fingerprint tokens. The CSS animation '#cmsg' is set to remain invisible (opacity:0) for 1.5 seconds, a known technique to delay display of cloaking messages. The combination of encoded identifiers and timed opacity manipulation is consistent with obfuscation used in cloaking infrastructure. (location: page.html: inline <script> and <style> blocks, line 1)
curl https://api.brin.sh/domain/cashstar.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cashstar.com currently scores 44/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.