context safety score
A score of 43/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
A heavily obfuscated popunder/ad script is embedded in the page head (comment '<!-- Pubblicità Popunder -->'). The script uses a character-interleaving obfuscation technique to hide its logic: it builds a function name/string array by splitting and reordering characters, then dynamically reconstructs API calls, creates hidden iframes, intercepts document methods, and rewrites querySelector results. This is a classic technique used by malvertising networks to evade static analysis and inject unsolicited content or redirect users. (location: page.html:68 — inline <script data-cfasync="false"> immediately after '<!-- Pubblicità Popunder -->' comment)
malicious redirect
The obfuscated popunder script dynamically manipulates window/document references and rewrites querySelector calls to substitute a random variable name for 'document'. This enables transparent redirection or navigation hijacking by intercepting and altering link resolution at runtime, consistent with popunder ad networks that open unsolicited tabs/windows without explicit user intent. (location: page.html:68 — obfuscated popunder script block)
hidden content
The ad iframe sourced from '//ad.a-ads.com/2386840' is embedded with no border, no padding, and 'background-color: transparent', making it visually blend into the page. While A-ADS is a known crypto ad network, transparent iframes are commonly abused to serve clickjacking overlays or drive invisible ad impressions, and the network is associated with low-quality/potentially malicious ad inventory. (location: page.html:662 — <iframe data-aa='2386840' src='//ad.a-ads.com/2386840?size=300x250'>)
social engineering
The page displays an urgent donation banner in Italian asking users to donate via PayPal to renew servers for February and March. The appeal to urgency ('PERMETTERCI DI RINNOVARE I SERVER') and the use of PayPal pools is a common social engineering pattern to solicit money from users of piracy/streaming sites, where the legitimacy of the fundraiser cannot be verified. (location: page.html:285-290 — PayPal donation alert banner linking to https://www.paypal.com/pools/c/9mIsoTE0XV)
curl https://api.brin.sh/domain/animesaturn.cxCommon questions teams ask before deciding whether to use this domain in agent workflows.
animesaturn.cx currently scores 43/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.