context safety score
A score of 32/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.in renders a full Google CAPTCHA/reCAPTCHA challenge page with the title 'https://www.google.com/', Google branding, Google Terms of Service links, and Google support links. The domain blogspot.in is not an official Google domain, yet it serves content designed to appear as a legitimate Google interstitial page. (location: page.html:3, page.html:22-27)
malicious redirect
The CAPTCHA form contains a hidden 'continue' field with value 'https://www.google.com/' and the form action is 'index'. Upon CAPTCHA completion, the submitCallback function automatically submits the form, potentially redirecting users through the non-Google domain blogspot.in before reaching the stated destination. This intermediary redirect via a non-Google domain is suspicious. (location: page.html:7, page.html:14, page.html:17)
phishing
The page impersonates a Google automated traffic detection page on a non-Google domain (blogspot.in). It uses authentic-looking Google reCAPTCHA enterprise widgets, Google policy language, and Google support URLs to create a convincing fake Google checkpoint, which could be used to harvest reCAPTCHA tokens or trick users into submitting data to a non-Google server. (location: page.html:1-35)
hidden content
The page contains a hidden div (id='infoDiv') with display:none that is only revealed on user interaction. Additionally, there is a hidden input field 'q' containing an opaque encoded token value, and a hidden 'continue' redirect URL. These hidden fields are submitted to the form endpoint without user visibility. (location: page.html:17, page.html:26)
prompt injection
The page title is set to 'https://www.google.com/' rather than a descriptive title. An AI agent crawling or summarizing this page by title would incorrectly attribute the content to google.com, not blogspot.in. This mismatch between the actual domain and the title/content could mislead AI agents into trusting or misclassifying the page origin. (location: page.html:3)
curl https://api.brin.sh/domain/blogspot.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
blogspot.in currently scores 32/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.