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 gadis-desa.online is serving a page that fully impersonates Google's CAPTCHA/unusual traffic detection page, including Google branding, Google reCAPTCHA Enterprise script, Google Terms of Service links, and text copied verbatim from Google's bot-detection interstitial. The page title is set to 'https://www.google.com/' to further deceive users and crawlers into believing they are on a Google property. (location: page.html:3-34, title tag and body content)
phishing
A non-Google domain (gadis-desa.online) is presenting a cloned Google CAPTCHA interstitial page. The form posts to 'index' (same domain) with a hidden 'q' parameter containing a base64-like token and a hidden 'continue' field pointing to https://www.google.com/. This is a classic phishing flow: deceive the user into submitting the CAPTCHA form on the attacker's domain, harvesting the interaction and then redirecting to Google to appear legitimate. (location: page.html:7,17)
malicious redirect
The hidden form field 'continue' is set to 'https://www.google.com/' and the form action posts to 'index' on the attacker-controlled domain. After form submission the user is redirected to Google, masking the fact that their interaction was processed by the malicious domain. This open-redirect pattern is used to launder the attack and reduce suspicion. (location: page.html:17 - <input type="hidden" name="continue" value="https://www.google.com/">)
social engineering
The page uses authoritative, fear-inducing language copied from Google ('Our systems have detected unusual traffic', 'violation of the Terms of Service', 'malicious software') to pressure users into completing the fake CAPTCHA, lowering their guard and increasing the likelihood of interaction with the attacker-controlled form. (location: page-text.txt:21-24)
hidden content
A hidden input field named 'q' carries a long opaque token value ('EhAmABkAAAAtCQAAAAAAABwBGM...') submitted silently with the form POST. This token is not visible to the user and its purpose is undisclosed; it may encode session tracking, victim fingerprinting, or a server-side payload identifier used by the attacker's backend. (location: page.html:17 - <input type='hidden' name='q' value='EhAmABkAAAAt...'>)
prompt injection
The page title is set to the string 'https://www.google.com/' rather than a descriptive title. AI agents that crawl or summarize pages by reading the <title> tag would incorrectly classify this page as belonging to google.com, causing them to treat the malicious domain as trusted and potentially bypass security checks or follow embedded instructions under the false context of a Google page. (location: page.html:3 - <title>https://www.google.com/</title>)
curl https://api.brin.sh/domain/gadis-desa.onlineCommon questions teams ask before deciding whether to use this domain in agent workflows.
gadis-desa.online 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.