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 hosted on blogspot.de impersonates Google's CAPTCHA/traffic-check page. The HTML title is set to 'https://www.google.com/', the page text mimics Google's 'unusual traffic' detection messaging verbatim, and the form's hidden 'continue' field redirects to https://www.google.com/. This creates a convincing fake Google security page on a non-Google domain. (location: page.html:3,17,30 — <title>, hidden input 'continue', displayed URL)
malicious redirect
The CAPTCHA form posts to 'index' (relative URL on blogspot.de) with a hidden 'q' parameter containing an encoded token, and a hidden 'continue' value of 'https://www.google.com/'. After the user completes the CAPTCHA, the flow is controlled by the operator of blogspot.de before any redirect to Google occurs. The encoded 'q' value may carry tracking or session-hijacking data. (location: page.html:7,17 — form action='index', hidden inputs 'q' and 'continue')
social engineering
The page uses authoritative Google-branded language ('Our systems have detected unusual traffic', 'violation of the Terms of Service') to pressure users into completing a CAPTCHA on a third-party domain (blogspot.de). This social pressure tactic is designed to lower user suspicion and drive form submission to an attacker-controlled endpoint. (location: page.html:24,27 — visible body text)
prompt injection
The page body contains an onload JavaScript handler: 'if(solveSimpleChallenge){solveSimpleChallenge(0,0);}'. This attempts to invoke a function named 'solveSimpleChallenge', which is not defined in the page. This pattern is consistent with attempts to hook or manipulate AI agents or browser automation frameworks that expose such global functions, instructing them to auto-solve challenges without user interaction. (location: page.html:4 — <body onload> attribute)
hidden content
An 'infoDiv' element is set to 'display:none' by default and only revealed on user click. While this pattern exists on the real Google CAPTCHA page, in this impersonation context it conceals supplementary messaging that reinforces the fake Google framing and may contain additional social engineering content invisible on initial render. (location: page.html:26 — <div id='infoDiv' style='display:none'>)
curl https://api.brin.sh/domain/blogspot.deCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.de 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.