context safety score
A score of 28/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
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
Site operates as an unauthorized free streaming platform distributing copyrighted content (HD films, series) without licensing, enticing users with free HD/4K access to popular titles. This creates a social-engineering lure that drives user registration and credential submission on a site with no verifiable legal standing. (location: page.html:8, page-text.txt:475, page.html:1113-1115)
credential harvesting
The site presents login (username + password), registration (email, username, password x2), and password-reset (email) modal forms that POST credentials to /login/, /register/, and /login/forgotPass/ endpoints on an unverified piracy domain. Users are encouraged to create accounts and submit personal credentials to a site with no WHOIS transparency (privacy redacted unknown, domain age unknown). (location: page.html:1170-1243, page-text.txt:1128-1196)
malicious redirect
Footer SEO text contains an outbound link to a third-party domain (https://www.fullhdfilmizlesene.so/film) with target="_blank" and anchor text 'film izle', silently redirecting users to a different piracy/potentially malicious domain. The .so TLD (Somalia) is commonly associated with high-risk domains. (location: page.html:1160)
hidden content
Multiple HTML comments containing only the word 'wait' are scattered throughout the page (at least 20 instances), used as server-side template placeholders that may indicate dynamically injected content blocks (e.g., ads, scripts, tracking) not present in the static snapshot. The footer link section between FOOTER LINKLER: BEGIN and END is completely empty, suggesting content was stripped or is conditionally loaded. (location: page-hidden.txt:1-36, page.html:1152-1154)
social engineering
The 'Film İstekleri' (Film Requests) feature invites users to submit content requests, increasing engagement and session time on a piracy site, normalizing continued use and increasing likelihood of credential submission or exposure to malicious ads. (location: page.html:958-969, page-text.txt:919-921)
obfuscated code
The inline script at page load (line 31) uses a minified, obfuscated block that sets cookies, conditionally modifies CSS layout based on a function _cg('go3'), and injects dynamic style elements. The function _cg is not defined in the visible HTML, suggesting it is loaded externally or injected at runtime. The cookie-setting function _cs writes a persistent 365-day cookie to the root domain. This pattern is consistent with ad-network or tracking fingerprinting scripts that conditionally activate based on user/session state. (location: page.html:31-34)
hidden content
All lazy-loaded images use a transparent SVG placeholder as the initial src attribute (data:image/svg+xml,...), which is standard practice, but combined with the 'wait' comment placeholders and empty footer link block, indicates significant portions of the page content are loaded asynchronously and not captured in the static scan, potentially including ad frames or tracking pixels. (location: page.html:157, 176, 195 (pattern repeated throughout))
curl https://api.brin.sh/domain/hdfilmizle.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
hdfilmizle.to currently scores 28/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.