context safety score
A score of 40/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
The page at blogspot.fr renders a full Google CAPTCHA/unusual-traffic page, including Google branding, Google reCAPTCHA enterprise widget, and Google Terms of Service links. The page title is set to 'https://www.google.com/' and all visible content mimics an official Google interstitial. This is a non-Google domain (blogspot.fr) impersonating Google's infrastructure to appear legitimate. (location: page.html:3-34, page-text.txt:19-27)
malicious redirect
The hidden form field 'continue' is set to 'https://www.google.com/' and the form action is 'index' (a relative path on blogspot.fr). After CAPTCHA completion, the submitCallback auto-submits the form to the blogspot.fr 'index' endpoint — not to Google — before any redirect occurs. This intercepts the CAPTCHA token and user interaction on a third-party domain under the guise of redirecting to Google. (location: page.html:17)
credential harvesting
The reCAPTCHA enterprise widget is loaded with a custom sitekey ('6LfwuyUTAAAAAOAmoS0fdqijC2PbbdH4kjq62Y1b') registered to the blogspot.fr operator, not Google. The CAPTCHA token generated upon completion is submitted via POST to the blogspot.fr 'index' endpoint, allowing the site operator to harvest valid reCAPTCHA enterprise tokens and associated user/network fingerprints. (location: page.html:15-17)
social engineering
The page uses authoritative Google language ('Our systems have detected unusual traffic', 'violation of Terms of Service', 'block will expire') to create urgency and compel the user to interact with and submit data to a non-Google controlled form on blogspot.fr. This social engineering pattern pressures users into completing the CAPTCHA without questioning the domain mismatch. (location: page.html:24-28, page-text.txt:21-24)
hidden content
An 'infoDiv' element is hidden by default (style='display:none') and contains additional social engineering text designed to explain and normalize the unusual traffic block. It is not visible on page load and only appears on user interaction, concealing part of the deceptive narrative from casual inspection. (location: page.html:26-28)
curl https://api.brin.sh/domain/blogspot.frCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.fr currently scores 40/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.