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 is hosted on blogspot.nl (a non-Google domain) but displays Google's CAPTCHA UI, Google branding, Google's Terms of Service links, and the page title 'https://www.google.com/' — impersonating a legitimate Google interstitial page to deceive users and automated agents into believing they are interacting with Google infrastructure. (location: page.html:3, page.html:22-28)
malicious redirect
The hidden form field 'continue' contains a hardcoded redirect to 'https://www.google.com/' and the form action posts to 'index' on the current non-Google domain. A CAPTCHA submission on a third-party domain (blogspot.nl) that mimics Google's challenge page is a classic redirect-after-credential-harvest pattern, routing users through an attacker-controlled domain before forwarding them onward. (location: page.html:17)
prompt injection
The page mimics a Google automated-traffic detection page with an 'onload' script calling 'solveSimpleChallenge(0,0)' — an attempt to instruct AI agents or headless browsers to auto-solve the challenge without user interaction. This targets agentic systems that parse and act on page instructions, coercing them to submit the form autonomously. (location: page.html:4)
social engineering
The page fabricates a Google security warning ('Our systems have detected unusual traffic from your computer network') and displays a specific IP address and timestamp to create false urgency and legitimacy, pressuring users or agents to complete the CAPTCHA and submit the form on a non-Google domain. (location: page.html:24, page.html:30)
hidden content
Two hidden input fields are embedded in the form: one named 'q' with an opaque encoded token value, and one named 'continue' with a redirect URL. These are not visible to the user and are silently submitted with the form POST to the attacker-controlled 'index' endpoint on blogspot.nl. (location: page.html:17)
curl https://api.brin.sh/domain/blogspot.nlCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.nl 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.