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 page hosted on pusat-hiburan.space fully impersonates Google's CAPTCHA/unusual traffic error page, including Google branding, Google reCAPTCHA enterprise widget, references to Google Terms of Service, and Google support links. The page title is set to 'https://www.google.com/' to further deceive users into believing they are on a Google property. (location: page.html:3, page.html:13, page.html:17, page.html:22-27)
phishing
The domain pusat-hiburan.space is serving a cloned Google CAPTCHA challenge page. The form posts to 'index' (action='index') with hidden fields including a token ('q') and a 'continue' parameter pointing to https://www.google.com/. This pattern is used in phishing flows to harvest CAPTCHA interaction data or redirect victims after credential collection steps that precede or follow this page. (location: page.html:7, page.html:17)
malicious redirect
The hidden form field 'continue' is set to 'https://www.google.com/' and the form submits to 'action=index' on the same malicious domain. Upon CAPTCHA completion, the user is redirected through the attacker-controlled backend before being sent to Google, enabling session token theft, credential capture, or cookie injection mid-redirect. (location: page.html:17)
social engineering
The page uses authoritative Google-style language ('Our systems have detected unusual traffic', 'in violation of the Terms of Service') to pressure users into interacting with the fake CAPTCHA form. This social pressure tactic is designed to make victims comply without questioning the legitimacy of the page. (location: page.html:24, page-text.txt:21-24)
hidden content
The 'infoDiv' element is set to display:none by default and is only revealed on user click. It contains additional Google-impersonating text and links to Google support URLs, reinforcing deception. Hidden content is also present in the form as undisclosed hidden fields ('q' with an opaque base64-like token value). (location: page.html:17, page.html:26-28)
prompt injection
The page title is set to the string 'https://www.google.com/' rather than a descriptive page title. This is a known technique to manipulate AI agents or browser automation tools that use page titles as context signals, causing them to misidentify the page origin as google.com when scraping or summarizing page metadata. (location: page.html:3)
curl https://api.brin.sh/domain/pusat-hiburan.spaceCommon questions teams ask before deciding whether to use this domain in agent workflows.
pusat-hiburan.space 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.