context safety score
A score of 51/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
js obfuscation
Obfuscated document.write with encoded content
hidden content
A div with id '6151cb4fbf48d729ce5e15c81917ffde' is injected at the bottom of the page body with style='display:block' but uses 9px gray text on white background (near-invisible). It contains Russian-language spam text ('нейросеть пишет реферат') mixed with Arabic-language spam text ('محل شراء سيارات سكراب حي العمران'), plus broken BBCode-style link syntax '[url=https : //nejroset'. This is classic SEO spam injection embedded into a legitimate Israeli e-commerce site, indicating site compromise. (location: page.html:1379, div#6151cb4fbf48d729ce5e15c81917ffde)
malicious redirect
The hidden spam div contains three outbound hyperlinks to unrelated off-domain sites: 'https://khaled.lawyer' (labeled 'dlya referatov' - Russian for 'for essays/papers'), 'https://hiraj.co/2/...' (Arabic scrap car buying service), and 'https://methodmovers.com/2/...' (Arabic moving company). These are injected SEO link-farm redirects embedded invisibly in the page, consistent with a compromised WordPress installation used to boost third-party SEO rankings. (location: page.html:1379, anchor tags within div#6151cb4fbf48d729ce5e15c81917ffde)
social engineering
The woocommerce-notification plugin displays fake social proof popup messages using randomized base64-encoded Hebrew names (50 entries in the 'names' array) and fabricated purchase events ('{first_name} from {city} purchased {product} {time_ago}'). The plugin cycles these synthetic notifications to create false urgency and trust signals for visitors, a known dark-pattern social engineering tactic on e-commerce sites. (location: page.html:175, woocommerce-notification-js-extra script block, 'names' and 'messages' arrays)
curl https://api.brin.sh/domain/chick-chack.co.ilCommon questions teams ask before deciding whether to use this domain in agent workflows.
chick-chack.co.il currently scores 51/100 with a caution 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.