context safety score
A score of 41/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 conditionally redirects based on referrer or user-agent
obfuscated code
Large inline script uses a Caesar-cipher-style character rotation obfuscation to decode and execute a string payload at runtime. The technique involves a scrambled string 'm' decoded via charCodeAt arithmetic, then used to build dynamic property names and URLs. This pattern is characteristic of malvertising loaders and click-fraud scripts that hide their true purpose from static analysis. (location: page.html, line 724)
malicious redirect
Third-party script loaded from 'bobsleddomesticglandular.com/on.js' — a domain with a randomly-assembled, nonsensical name (classic domain generation algorithm / ad-fraud pattern). It is loaded with data-cfasync='false' to bypass Cloudflare filtering, and its onload/onerror callbacks invoke an undeclared global function 'archxtu(15)', suggesting it orchestrates further payload execution or redirect logic. (location: page.html, line 725)
malicious redirect
Two ad-tag scripts loaded from '//aqle3.com/btag.min.js' (a known ad-network domain associated with aggressive ad injection and potential malvertising). Loaded via protocol-relative URLs, bypassing mixed-content warnings, and flagged data-cfasync='false' to avoid Cloudflare scrutiny. (location: page.html, lines 4278 and 7620)
obfuscated code
The inline obfuscated script references a global 'handleException' variable as a conditional hook and uses dynamic string construction to assemble URLs and object keys at runtime, making static analysis of its network destinations impossible without execution. (location: page.html, line 724)
curl https://api.brin.sh/domain/animeworld.acCommon questions teams ask before deciding whether to use this domain in agent workflows.
animeworld.ac currently scores 41/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.