context safety score
A score of 48/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
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
The page contains a heavily obfuscated JavaScript function named 'xXRQBR' with a large array of encoded/scrambled string tokens. This is a common obfuscation pattern used to hide malicious logic from static analysis tools, including WAF bypasses and fingerprinting scripts. (location: page.html - inline <script name='aliyunwaf_6a6f5ea8'>)
hidden content
A hidden <textarea id='renderData'> element with display:none contains embedded JSON including a JavaScript variable assignment string ('var arg1=...') and an HTTP method directive ('GET'). This data is extracted and executed at runtime by inline scripts, hiding the actual execution parameters from casual inspection. (location: page.html - <textarea id='renderData' style='display:none'>)
malicious redirect
The page contains a 'reload()' function that reads document.referrer, appends it as 'alichlgref' query parameter, and redirects the browser to a reconstructed URL. This silently leaks the referring URL to the server and can be used to track user navigation or redirect users after cookie manipulation. (location: page.html - inline <script> reload() function)
hidden content
The Aliyun WAF anti-bot challenge sets a cookie 'acw_sc__v2' with a computed value derived from obfuscated JavaScript execution. While this is a known CDN/WAF anti-bot mechanism, the opaque computation and forced cookie injection constitute non-transparent client-side behavior that AI agents and automated browsers would execute without visibility into what is being computed or transmitted. (location: page.html - setCookie('acw_sc__v2', ...) in inline script)
curl https://api.brin.sh/domain/taptap.cnCommon questions teams ask before deciding whether to use this domain in agent workflows.
taptap.cn currently scores 48/100 with a suspicious verdict and medium 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.