context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
The page is served from watchmovierulz.fish but all internal links, canonical tag, favicon, stylesheet, and search form action redirect to a different domain: www.watchmovierulz.pink. The .fish domain acts as a shadow/mirror entry point that silently routes all user interactions to the .pink domain, concealing the true destination. (location: page.html:17,32,33,34,51,55,66 — canonical href, shortlink, favicon, stylesheet, all nav hrefs pointing to watchmovierulz.pink)
brand impersonation
The site impersonates 'MovieRulz', a well-known piracy brand, using the name 'Movierulz' in the title tag and 'MovieRulz' throughout content and branding. The .fish TLD combined with cross-domain mirroring to .pink indicates a copycat/clone operation designed to capture traffic under a fraudulent alternate domain while impersonating the primary piracy brand. (location: page.html:15 (title tag), page.html:51 (site-title), page.html:461 (footer))
social engineering
The site promotes free streaming and downloading of copyrighted movies (Bollywood, Hollywood, Telugu, Tamil, Malayalam) including pirated cam/DVD rips (DVDScr, DVDRip, HDRip, BRRip), enticing users with free premium content to drive traffic through potentially malicious redirects or ad monetization. The footer disclaimer attempts to legally distance the site from liability while continuing to facilitate piracy. (location: page.html:462-463 (footer disclaimer), page.html:197,288 (Featured Movies Free, Latest Movies sections))
malicious redirect
A Telegram channel link (https://telegram.me/watchmovierulzofficial/) is embedded in the sidebar, directing users to an external messaging platform under the guise of a download/watch button. This is a common vector for distributing malware, harvesting contacts, or further social engineering off-platform. (location: page.html:432 (sidebar widget, ad_watch_now link to telegram.me/watchmovierulzofficial/))
curl https://api.brin.sh/domain/watchmovierulz.fishCommon questions teams ask before deciding whether to use this domain in agent workflows.
watchmovierulz.fish currently scores 46/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.