context safety score
A score of 77/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
js obfuscation
Very long base64 or hex string assigned in JavaScript — likely encoded payload
hidden content
Page title and all SEO metadata (og:title, twitter:title, meta description) are spoofed to read '() Stock Price, Quote & News' / 'Find latest stock, quote, financials and news to help you trade better' — completely unrelated to the actual page content (Italian construction/eco initiative). The robots meta is set to nofollow/noindex. This is content cloaking: metadata presented to crawlers and AI agents differs from what human visitors see, designed to deceive automated consumers of the page. (location: page.html lines 371-390, <title> and <meta> tags injected by Rank Math SEO plugin)
hidden content
The 'massive-stock-widgets' WordPress plugin is loaded (CSS and JS assets) and its configuration object (mstocks) is injected into the page, yet no stock widget renders in the visible content. This plugin appears to be the vehicle for injecting the fraudulent stock-ticker SEO metadata without any visible widget to justify its presence. (location: page.html lines 449-450, 539, 1055, 2189-2194)
hidden content
Multiple elements are hidden via CSS: '.heading-title { display: none; }' hides the H1 heading from users, and '.before-footer { display: none; }' hides a footer section. These reinforce the cloaking pattern where content visible to crawlers differs from what users see. (location: page.html lines 13-14 and 2082-2083)
social engineering
JavaScript on DOMContentLoaded captures the visitor's document.referrer and stores it in a cookie named 'newarrivo' with a 30-day expiry. This silently tracks where users came from without explicit disclosure in the visible consent flow, enabling audience profiling and retargeting. (location: page.html lines 600-622)
curl https://api.brin.sh/domain/condominiocherespira.itCommon questions teams ask before deciding whether to use this domain in agent workflows.
condominiocherespira.it currently scores 77/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.