context safety score
A score of 34/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
The page is served from fullhdfilmizlesene.tv but all internal links, canonical tag, og:url, and dns-prefetch directives point to fullhdfilmizlesene.live. The .tv domain silently funnels users to the .live domain, a classic domain-shadowing/redirect pattern used to evade blocklists while maintaining a secondary domain for traffic capture. (location: page.html:11,22,24,25 - og:url, canonical, rel=next, dns-prefetch all reference fullhdfilmizlesene.live while the scanned URL is fullhdfilmizlesene.tv)
social engineering
The site promotes a downloadable Android APK ('Mobil Uygulamamız kullanıma hazırdır - Buradan İndir') hosted at fullhdfilmizlesene.live/mobil-uygulama-apk-2. Distributing sideloaded APKs outside official app stores is a well-established vector for malware delivery, exploiting users' desire for free HD film streaming. (location: page.html:252-255 - duyuru-box APK download link)
malicious redirect
A hidden div with class 'ajax-data' carries a large base64/obfuscated data-id attribute value and data-no attribute, rendered with the 'hidden' HTML attribute. This pattern is commonly used to pass encoded redirect or configuration payloads to client-side JavaScript without visibility to users or basic scanners. (location: page.html:936 - <div class='ajax-data' data-id='PUUQYNkUC5RDPMhQb9BAXFgUBcVATJFUAcwUTN1BEIQCJQ1UQN1BQFAVXdFUF4hQe4lHZJFVF9BBBEQXWB1HDIEHFdkUe4xCCFURFl1EMI1QCFhUfhkQQFRRBh1QSJUD' data-no='4' hidden>)
hidden content
The hidden div with encoded data-id attribute contains an opaque encoded string not rendered to users. Its content and purpose are not disclosed in the visible HTML; it is consumed by external JavaScript bundles (alljs, ftjs) loaded from minified/versioned paths, making its function unauditable from the HTML alone. (location: page.html:936 - hidden ajax-data div with encoded data-id payload)
social engineering
The site distributes copyrighted Hollywood and international films (Superman, Mission Impossible, Jurassic World, Fantastic Four, etc.) without authorization, presenting them as freely available in HD/4K. This creates a trust environment that lowers user guard, making users more susceptible to malicious APK downloads, ad fraud, or credential harvesting via the login ('Giriş') flow. (location: page.html:208 - login button href='#'; entire film listing across page.html:269-706)
obfuscated code
JavaScript bundles are loaded from versioned minified paths (/minx/alljs.1752088924.js, /minx/ftjs.1760371771.js) with no inline content visible for audit. The alljs bundle is preloaded in <head> before any content renders, giving it full DOM access. Combined with the hidden encoded ajax-data div, these scripts can execute undisclosed behavior including redirects, ad injection, or data exfiltration. (location: page.html:14,125,888 - preload and script src for alljs and ftjs bundles)
malicious redirect
JavaScript sets siteUrl and siteDom variables to fullhdfilmizlesene.live (not .tv, the domain being visited), and the proto variable dynamically selects http/https. This JS-level domain substitution supports programmatic cross-domain redirect or resource loading logic that differs from the served domain. (location: page.html:117-124 - inline script block setting siteUrl='https://www.fullhdfilmizlesene.live' and siteDom='fullhdfilmizlesene.live')
curl https://api.brin.sh/domain/fullhdfilmizlesene.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
fullhdfilmizlesene.tv currently scores 34/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.