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 google.to is impersonating Google by using Google branding, Google reCAPTCHA Enterprise, Google Trust Services TLS certificate, and Google-styled CAPTCHA challenge page. The page mimics a legitimate Google interstitial to appear trustworthy, while the domain is a Tonga ccTLD with no affiliation to Google LLC. (location: metadata.json:domain, page.html:1-35)
phishing
The page presents a fake Google CAPTCHA interstitial on a non-Google domain (google.to). This is a classic phishing lure: users believe they are interacting with Google infrastructure, which can be used to harvest tokens, session data, or redirect users to malicious payloads after CAPTCHA completion. The hidden 'continue' field points back to https://google.to/ and the 'q' field contains an opaque encoded token. (location: page.html:17)
credential harvesting
A POST form (id='captcha-form') submits to 'index' with hidden fields including an opaque base64-like token in field 'q' and a 'continue' redirect URL. This pattern is used in credential harvesting flows where CAPTCHA completion triggers a redirect to a login page or silently exfiltrates session/identity tokens. (location: page.html:7,17)
social engineering
The page uses authoritative, fear-inducing language ('Our systems have detected unusual traffic from your computer network') to pressure users into completing the CAPTCHA without questioning the legitimacy of the domain. The IP address and timestamp are displayed to add false credibility and urgency. (location: page.html:24,30)
prompt injection
The onload attribute executes 'solveSimpleChallenge(0,0)' if the function exists in the page context. This is a form of prompt/script injection targeting automated agents or headless browsers: if an AI agent or bot framework exposes such a function, this call could manipulate the agent into auto-solving and submitting the challenge without user interaction. (location: page.html:4)
curl https://api.brin.sh/domain/google.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
google.to 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.