context safety score
A score of 36/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 domain blogspot.co.at serves a page that visually and textually impersonates Google's CAPTCHA/robot-check interstitial. The page title is set to 'https://www.google.com/', the content references 'Google' systems, Google Terms of Service, and Google support links, while the actual serving domain is blogspot.co.at — a non-Google domain designed to deceive users into believing they are interacting with a legitimate Google security page. (location: page.html:3, page.html:22-28)
phishing
The page mimics a Google automated traffic/CAPTCHA challenge page hosted on a non-Google domain (blogspot.co.at). The form POSTs to 'index' with hidden fields including a 'continue' parameter set to 'https://www.google.com/', a classic phishing pattern used to capture CAPTCHA responses or redirect victims after credential/token submission under the guise of a Google security check. (location: page.html:7, page.html:17)
malicious redirect
The form contains a hidden 'continue' field with value 'https://www.google.com/' used as a redirect destination after form submission. Combined with the non-Google hosting domain, this is consistent with a phishing flow that processes the victim's submission before redirecting to the legitimate Google site to reduce suspicion. (location: page.html:17)
social engineering
The page employs social engineering by presenting an urgent 'unusual traffic detected' message attributed to Google systems, instructing the user to solve a CAPTCHA to 'continue using our services.' This creates false urgency and authority to pressure users into interacting with the fake CAPTCHA form on a non-Google domain. (location: page.html:24-27, page-text.txt:21-24)
prompt injection
The page title is set to the literal string 'https://www.google.com/' rather than a descriptive title. AI agents that ingest page metadata or titles to determine page identity/trustworthiness could be misled into treating this page as belonging to google.com, effectively injecting a false URL identity into agent context via the title tag. (location: page.html:3)
hidden content
The 'infoDiv' element is set to 'display:none' by default and only revealed via an onclick handler. This div contains additional social engineering text and links referencing Google Terms of Service and support pages. Hidden content is used to conceal secondary manipulation layers from cursory inspection while remaining accessible to users who interact with the page. (location: page.html:26-28)
curl https://api.brin.sh/domain/blogspot.co.atCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.co.at currently scores 36/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.