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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
Obfuscated document.write with encoded content
malicious redirect
Multiple navigation links point to third-party affiliate/ad redirect domains (g.ieeod0.com, tp.9377o.com, tp.9377s.com, yxtg.taojike.com.cn, code.caihong.com) disguised as in-site game listings. These are tracking redirectors with uid/sid parameters that route users through unknown intermediaries before reaching destinations. 15 such links identified. (location: page.html lines 377-482, 4795 — 'hot games' and 'web games' sections)
hidden content
A <div style='display:none'> block wraps a Baidu analytics script (hm.baidu.com) loaded via document.write with URL-encoded unescape() call, obscuring the loaded resource from casual inspection. The encoding is a standard obfuscation pattern even if the destination (Baidu analytics) is benign in this context. (location: page.html lines 6372-6379)
social engineering
Multiple prominently placed ad links use deceptive title attributes that differ from visible link text (e.g. title='超超超变鬼服' but displays '霸刀·玩转搜打撤'; title='山河图志' but displays '免费BT版传世'; title='首发·九职业传奇' but displays '2026打金传奇'). This mismatch between tooltip/accessibility text and displayed text is a social engineering technique to mislead users and potentially AI agents parsing link metadata. (location: page.html lines 377, 473, 478, 482 — advertisement anchor elements)
hidden content
Inline <style> tag sets font-size:0!important on a navigation link's anchor text (.change6 a), making the link text '游侠加速器' visually invisible while preserving it in the DOM. The link text is hidden and replaced by a background image, concealing the true link label from text-based parsers. (location: page.html line 368 — .change6 navigation item)
curl https://api.brin.sh/domain/ali213.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
ali213.net 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.