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
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
JavaScript on line 65 of page.html uses base64 (atob) decoding combined with character-code arithmetic obfuscation to dynamically compute a window property key name ('ZIProjectKey') and a script src URL ('https://js.zi-scripts.com/zi-tag.js') before injecting and loading that external script. While zi-scripts.com is associated with ZoomInfo B2B visitor identification, the obfuscation technique conceals the third-party script being loaded and is atypical for a legitimate site implementation. (location: page.html, line 65)
malicious redirect
The scanned domain is chicoryapp.com, but every canonical URL indicator in the page points to a different domain: canonical href='https://chicory.co', og:url='https://chicory.co', twitter:url='https://chicory.co', itemprop url='https://chicory.co', and the Squarespace site context sets authenticUrl, baseUrl, and primaryDomain all to 'chicory.co'. This means chicoryapp.com is serving a full mirror of the chicory.co site, which is a classic domain-squatting or traffic-hijacking pattern where users directed to the alternate domain receive the legitimate site's content without realizing they are on a different domain. (location: page.html lines 11, 14, 21, 28; metadata.json)
brand impersonation
The domain chicoryapp.com hosts a complete copy of the Chicory (chicory.co) corporate website — including the Chicory logo, branding, navigation, content, and contact information — without being the legitimate chicory.co domain. The Squarespace site identifier 'quillfish-tulip-83mk' and all internal references confirm this is the actual Squarespace backend for chicory.co being served under an alternate domain. An end user or AI agent browsing chicoryapp.com would believe they are on the official Chicory website when the actual registered brand domain is chicory.co. (location: page.html lines 6, 553, 929; metadata.json domain field)
curl https://api.brin.sh/domain/chicoryapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
chicoryapp.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.