context safety score
A score of 31/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
obfuscated code
A heavily obfuscated JavaScript block is injected inside a hidden div (display:none). The code uses a character-interleaving obfuscation technique on a long string that is split, re-ordered, and then used to reconstruct and call DOM/window APIs dynamically. It manipulates document references, overrides querySelector, createElement, and addEventListener, creates a sandboxed iframe to isolate execution context, and rewrites document-level methods. This pattern is consistent with anti-bot/fingerprinting or click-hijacking payloads designed to evade static analysis. (location: page.html:65-67, inside <div style='display: none;'>)
hidden content
Multiple Google Analytics tracking scripts (UA-269945118-1, G-6ZDPCTTMZN, UA-269945118-2) are injected inside a <div style='display: none;'> block at the bottom of the page. Hiding tracking/analytics scripts in invisible containers is atypical and may be used to conceal third-party data exfiltration from content scanners. (location: page.html:1367-1405, <div style='display: none;'>)
malicious redirect
The page is served from topcinema.rip but all internal links, canonical tag, og:url, schema.org URLs, font/asset loads, favicon, and JavaScript variable HomeURL all point to topcinema.fan. The canonical URL explicitly redirects authority to a different domain. Users (and agents) landing on topcinema.rip are transparently operated as a mirror/doorway page for topcinema.fan, which is a classic domain-shadowing or doorway-page pattern used to funnel traffic and potentially serve different content to different visitors. (location: page.html:45 (canonical), line 9-14 (fonts), line 1417 (HomeURL JS var))
brand impersonation
The site references and heavily promotes Netflix-branded content (افلام نتفليكس, مسلسلات نتفليكس, اجنبي نتفلكس, انمي نتفلكس) throughout navigation menus and dedicated content sections, implying affiliation with or authorization by Netflix. The site is an unauthorized piracy platform, not affiliated with Netflix, constituting brand impersonation to attract users. (location: page.html:80, 88, 96, 104, 161, 1192-1194 (Netflix menu/section labels))
hidden content
The obfuscated script block and all three Google Analytics tags are wrapped in <div style='display: none;'>, making them invisible to human visitors but executable by browsers and potentially readable/triggered by AI agents crawling the DOM. This is a standard technique to hide tracking or malicious payloads from casual inspection. (location: page.html:65 and 1367)
curl https://api.brin.sh/domain/topcinema.ripCommon questions teams ask before deciding whether to use this domain in agent workflows.
topcinema.rip currently scores 31/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.