context safety score
A score of 34/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 pohonemas33.website is masquerading as a Google security/CAPTCHA page. The page title is set to 'https://google.com/', the content mimics Google's 'unusual traffic' CAPTCHA interstitial verbatim, referencing Google Terms of Service and Google support links, while the hosting domain has no affiliation with Google. (location: page.html:3, page.html:22-28)
phishing
The domain pohonemas33.website hosts a fake Google CAPTCHA page designed to deceive users into believing they are on a legitimate Google property. The form posts to 'index' with a hidden 'continue' field pointing to https://google.com/, creating a convincing phishing flow that could harvest tokens or redirect users after form submission. (location: page.html:7, page.html:17)
malicious redirect
A hidden form field named 'continue' contains the value 'https://google.com/', and the form posts to a local 'index' endpoint. This pattern is consistent with an open-redirect abuse or token-harvesting intermediary — the attacker's server at pohonemas33.website intercepts the CAPTCHA response before forwarding the user to Google, allowing collection of session tokens or reCAPTCHA tokens. (location: page.html:17)
credential harvesting
The reCAPTCHA Enterprise widget uses a site key (6LfwuyUTAAAAAOAmoS0fdqijC2PbbdH4kjq62Y1b) and a pre-populated data-s token registered to the attacker's domain, not Google. The CAPTCHA response token generated by the user is submitted via POST to pohonemas33.website/index, where it can be harvested and replayed or used to bypass bot protections on other services. (location: page.html:15, page.html:17)
hidden content
A hidden input field named 'q' contains a long opaque base64/encoded token value ('EhAmABkAAAAtBQAAAAAAADgBGP2Koc0GIikYwlPxMUpmPJkJBvI4SHtrEf3ZBzzJQdv4HqvWQaAxGdvtTvxmszH9YzICclJaAUM'). This hidden field is not visible to users and its purpose is concealed, consistent with session token exfiltration or anti-bot bypass payloads. (location: page.html:17)
social engineering
The page uses authoritative, fear-inducing language copied from genuine Google security pages ('Our systems have detected unusual traffic', 'malicious software', 'violation of Terms of Service') to pressure users into complying with the CAPTCHA prompt on an attacker-controlled domain, lowering their guard and increasing form submission likelihood. (location: page.html:24-28, page-text.txt:21-24)
curl https://api.brin.sh/domain/pohonemas33.websiteCommon questions teams ask before deciding whether to use this domain in agent workflows.
pohonemas33.website currently scores 34/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.