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 lihat-disini.fun fully impersonates Google's CAPTCHA/reCAPTCHA interstitial page, including Google branding, Google's exact error messaging ('Our systems have detected unusual traffic...'), links to google.com policies, and a forged reCAPTCHA widget. The page title is set to 'https://www.google.com/' to further deceive users into believing they are on Google's infrastructure. (location: page.html:3-33, title tag and full body content)
phishing
The domain lihat-disini.fun (meaning 'view here' in Indonesian/Malay) hosts a convincing fake Google CAPTCHA page. The form posts to 'index' with a hidden 'continue' parameter set to 'https://www.google.com/', creating a phishing flow where users believe they are completing a Google verification before being redirected. This is a classic CAPTCHA phishing lure used to harvest interaction data or serve as a redirect gateway. (location: page.html:7,17)
malicious redirect
The form contains a hidden input field named 'continue' with value 'https://www.google.com/'. After form submission (triggered by reCAPTCHA callback), the user is redirected. The actual redirect destination is controlled server-side via the 'index' action endpoint, not the client-side 'continue' value shown — the displayed google.com destination is likely a decoy. The hidden 'q' parameter contains an encoded/opaque token suggesting server-side tracking or redirect logic. (location: page.html:17, hidden inputs name='q' and name='continue')
hidden content
The page includes a hidden div with id='infoDiv' (display:none) that contains extended Google-branded explanatory text shown only on user interaction. Additionally, a hidden form field 'q' carries a long base64-like encoded value ('EhAmABkAAAAtBwAA...') that is not visible to the user and is submitted silently with the form, potentially encoding tracking identifiers, victim fingerprint data, or session tokens. (location: page.html:17 (hidden input q), page.html:26 (infoDiv display:none))
social engineering
The page employs Google's authentic CAPTCHA warning language verbatim to create urgency and legitimacy: 'Our systems have detected unusual traffic from your computer network.' It also displays a real-looking IP address and timestamp to convince users the block is genuine and that completing the CAPTCHA is necessary to restore access. This psychological pressure technique coerces user compliance. (location: page.html:24-31, page-text.txt:21-27)
prompt injection
The page title is set to the string 'https://www.google.com/' rather than a descriptive page title. AI agents that browse the web and use page titles as context signals for trust or classification could be misled into treating this page as if it were the legitimate Google homepage, bypassing threat assessment heuristics based on URL/title matching. (location: page.html:3, <title>https://www.google.com/</title>)
obfuscated code
The reCAPTCHA div contains an unusually long and non-standard 'data-s' attribute value ('g3eLi_udSmKMyTrw_uJQiXE56Us3XMTS7gokLx00vSRPx4e...') far exceeding what legitimate Google reCAPTCHA enterprise widgets use. This attribute appears to be custom/injected data, potentially used to pass encoded payload or exfiltrate session context to a backend server upon CAPTCHA completion. The onload handler also calls 'solveSimpleChallenge(0,0)' — a non-Google function — suggesting injected JS logic to auto-solve or bypass the challenge. (location: page.html:4 (onload solveSimpleChallenge), page.html:15 (data-s attribute on g-recaptcha div))
curl https://api.brin.sh/domain/lihat-disini.funCommon questions teams ask before deciding whether to use this domain in agent workflows.
lihat-disini.fun 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.