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.se renders content that fully impersonates a Google reCAPTCHA/bot-check interstitial. The page title is set to 'https://www.google.com/', the messaging mimics Google's automated traffic detection system, and the visual layout copies Google's CAPTCHA challenge page. The domain blogspot.se is not owned by Google, making this a deceptive impersonation of Google's brand and infrastructure. (location: page.html:3-33)
malicious redirect
A hidden form field sets 'continue' to 'https://www.google.com/' and the form posts to 'index'. After CAPTCHA completion, the submitCallback automatically submits the form. This pattern is consistent with a redirect chain where the victim is funneled through the attacker-controlled domain (blogspot.se) before being sent onward, allowing session data, tokens, or query parameters to be intercepted mid-flow. (location: page.html:17)
credential harvesting
The hidden form field 'q' contains a large opaque base64-like encoded token value. Combined with the fake Google CAPTCHA flow, this pattern is characteristic of credential or session-token harvesting intermediary pages, where the encoded value may carry OAuth state, session identifiers, or tracking data to be exfiltrated upon form submission. (location: page.html:17)
social engineering
The page uses authoritative, trust-inducing language copied from Google's legitimate bot-check pages ('Our systems have detected unusual traffic', 'violation of the Terms of Service') to pressure the user into completing the CAPTCHA challenge on a non-Google domain, lowering suspicion and increasing compliance. (location: page.html:22-28)
prompt injection
The page title is set to the string 'https://www.google.com/' rather than a descriptive title. An AI agent that indexes or summarizes page titles could be misled into treating this page as the legitimate Google homepage, causing the agent to take actions (e.g., marking the site as trusted, following links) based on a falsified identity signal embedded in page metadata. (location: page.html:3)
curl https://api.brin.sh/domain/blogspot.seCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.se 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.