context safety score
A score of 38/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site is hosted at aniwatchtv.to but consistently presents itself as 'AniWatch.to' in all branding, titles, meta tags, og:url, and copyright footer. The actual domain (aniwatchtv.to) impersonates the well-known AniWatch.to brand by mimicking its name, logo, and content to attract users searching for the legitimate site. (location: page.html: <title>, og:url, og:title, og:description, footer copyright — all reference 'AniWatch.to' while actual domain is aniwatchtv.to)
obfuscated code
A heavily obfuscated JavaScript block is present, using a character-interleaving string encoding technique (split/reduce alternating chars) to hide its logic. The decoded string array contains references to DOM manipulation (createElement, appendChild, innerHTML), localStorage, setTimeout/setInterval, MessageChannel, BroadcastChannel, localStorage.setItem/getItem, encodeURIComponent, ServiceWorker, and querySelector — indicative of anti-analysis, sandboxing evasion, or covert tracking/exfiltration logic. The try/catch wrapper suppresses all errors to avoid detection. (location: page.html:459-463, page-text.txt:374-376 — inline <script data-cfasync='false'> block)
social engineering
The page contains repeated trust-building claims ('safest site', 'we keep scanning ads 24/7', 'trustworthy and safe site') designed to lower user guard on a piracy/unofficial streaming site operating under a misleading domain. These claims are unverifiable and serve to socially engineer users into trusting the site with continued engagement. (location: page.html:173-222, page-text.txt:103-152)
curl https://api.brin.sh/domain/aniwatchtv.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
aniwatchtv.to currently scores 38/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.