context safety score
A score of 37/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 checks user-agent for bot/crawler strings to serve different content
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
js obfuscation
JavaScript appears to use a common packer pattern (p,a,c,k,e,d)
obfuscated code
Packed/obfuscated JavaScript using eval() with a Dean Edwards p,a,c,k,e,r packer. The decoded logic checks the user's browser language and, if Turkish ('tr' or 'tr-*'), replaces the current domain segment '.to' with '.life' and redirects to window.location. This is a cloaked language-based redirect that conceals its true behavior from static analysis. (location: page.html:38 — eval(function(p,a,c,k,e,r){...}))
malicious redirect
The unpacked script at line 38 performs a conditional redirect: if the browser language is Turkish ('tr' or starts with 'tr-'), it replaces the domain's '.to' TLD with '.life' and appends the current pathname+search, silently redirecting Turkish-language visitors to a different domain. This is a language-gated redirect hidden inside obfuscated code. (location: page.html:38 — packed script with domain replace and window.location redirect)
social engineering
The site presents itself as a legitimate free HD movie streaming platform with a professional UI, registration/login modals collecting username, password, and email, and well-known film titles and IMDb ratings. The '.life' TLD combined with a polished Turkish-language UI is a common pattern for unofficial piracy sites that harvest user accounts and expose users to ad-injected or malicious video embeds. (location: page.html:74-80 (login/register buttons), page.html:1342-1414 (login/register modals))
credential harvesting
The site collects username, password, and email address via AJAX POST to /login/ and /register/ endpoints on an unofficial streaming site with no visible privacy policy or legal entity. Credentials entered here are sent to an unverified third party. The domain uses a .life TLD and lacks any trust indicators beyond a basic DV TLS certificate. (location: page.html:1342-1414 (loginModal, registerModal, forgotPassModal forms); page.html:1500 ($.post('/login/',...)))
hidden content
A cookie named 'go7' is silently set after a 10-minute timeout using an obfuscated function _cs(), and a companion _cg() function gates the injection of additional CSS (nav margin adjustments and ad-slot height caps). This pattern is used to set tracking/ad-targeting cookies without user consent and to conditionally reveal ad content after a delay, evading immediate detection. (location: page.html:34-37 — window.rekAktif, _cg('go7'), _cs(cnx,1,365) setTimeout)
curl https://api.brin.sh/domain/hdfilmizle.lifeCommon questions teams ask before deciding whether to use this domain in agent workflows.
hdfilmizle.life currently scores 37/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.