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 domain google.im uses Google branding, Google reCAPTCHA enterprise scripts, Google Terms of Service links, and Google-style CAPTCHA challenge UI to impersonate Google Search. The .im ccTLD (Isle of Man) is not an official Google domain, yet the page fully mimics Google's automated traffic detection page. (location: https://google.im/ — page.html:3-35)
social engineering
The page presents a fabricated 'unusual traffic detected' scenario identical to Google's bot-detection page, pressuring users to interact with a CAPTCHA form. This social engineering technique exploits user trust in Google's infrastructure to compel form submission to a non-Google domain. (location: https://google.im/ — page.html:24-27)
phishing
The CAPTCHA form posts to 'index' (relative URL) via POST on a non-Google domain, with a hidden 'continue' field pointing back to https://google.im/. This pattern is consistent with a phishing relay that captures CAPTCHA tokens or session data before redirecting the user, mimicking a legitimate Google verification flow. (location: page.html:7,17 — form action='index' with hidden fields 'q' and 'continue')
malicious redirect
A hidden form field named 'continue' contains the value 'https://google.im/', which is used as a redirect target after form submission. Combined with the encoded 'q' parameter, this mirrors credential-harvesting redirect chains seen in phishing kits that bounce victims through intermediate domains. (location: page.html:17 — <input type='hidden' name='continue' value='https://google.im/'>)
prompt injection
The page body onload handler calls 'solveSimpleChallenge(0,0)' — a function not defined in the visible page source. This suggests an attempt to invoke an external or injected function, potentially targeting AI agents or browser automation that execute JavaScript, to silently auto-solve or auto-submit the CAPTCHA challenge without user interaction. (location: page.html:4 — onload="e=document.getElementById('captcha');if(e){e.focus();} if(solveSimpleChallenge) {solveSimpleChallenge(0,0);}")
curl https://api.brin.sh/domain/google.imCommon questions teams ask before deciding whether to use this domain in agent workflows.
google.im 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.