context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Domain '5movierulz.reisen' impersonates the well-known piracy brand 'MovieRulz', a widely recognized unauthorized movie streaming/download platform. The numeric prefix '5' and the use of a non-standard TLD '.reisen' (German for 'travel') are classic indicators of a copycat or mirror site attempting to capitalize on an established piracy brand's reputation and user base. (location: domain: 5movierulz.reisen)
social engineering
The site operates under the 'MovieRulz' brand identity, which is associated with illegal content distribution. Such sites routinely use social engineering tactics to coerce visitors into disabling ad-blockers, accepting notifications, or clicking through deceptive ad overlays in order to generate revenue or deliver malware. The domain pattern (numbered prefix + alternate TLD) is consistent with redirect/mirror networks used to funnel users through monetized threat chains. (location: domain: 5movierulz.reisen)
malicious redirect
The domain follows the well-documented 'MovieRulz' mirror site pattern where numbered variants (1movierulz, 2movierulz, etc.) serve as rotating redirect hubs. These sites typically chain visitors through multiple ad networks and redirect layers — including popunders, forced redirects, and traffic monetization intermediaries — before reaching any actual content. The use of the '.reisen' TLD is consistent with domains registered specifically for redirect/traffic arbitrage purposes. (location: domain: 5movierulz.reisen)
curl https://api.brin.sh/domain/5movierulz.reisenCommon questions teams ask before deciding whether to use this domain in agent workflows.
5movierulz.reisen currently scores 49/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.