context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
Third-party ad script loaded from suspicious domain 'bullionglidingscuttle.com' via non-HTTPS protocol-relative URL. This domain is unrelated to any known ad network and is characteristic of malvertising infrastructure used to redirect users to phishing or malware pages. (location: page.html:35 and page.html:599)
malicious redirect
Third-party script loaded from 'holahupa.com' — another unrecognized domain serving JavaScript directly into the page. Pattern matches known malvertising/redirect networks that can push popunders, forced redirects, or drive-by downloads. (location: page.html:689)
hidden content
Tracking beacon script assigned type 'b9d0551c15102fa02e1ba193-text/javascript' — a non-standard MIME type used by Cloudflare Rocket Loader to defer execution, but it covertly fires an image request to 'counter.yadro.ru' collecting referrer URL, screen dimensions, color depth, page URL, and page title without user awareness. This constitutes covert fingerprinting and data exfiltration. (location: page.html:691-697)
social engineering
Multiple video listings contain incest-themed titles and descriptions (step-son, step-mom, brother/sister, father/daughter 'baap beti') and non-consent framing ('sister forced', 'jabardasti' meaning 'by force'). These are used as SEO lures to attract vulnerable users and funnel them through ad networks that may serve scams or malware. (location: page.html:613-650, page-text.txt:590-634)
social engineering
'May be interesting' section links to a network of affiliated adult sites (myhdxxx.com, videozz.xyz, porno18.site, xnxxx.xyz, avxxx.site, trendvideo.xyz) forming a cross-promotion ring. These affiliate networks commonly monetize through deceptive ad overlays and credential-harvesting fake login prompts. (location: page.html:663-675)
hidden content
Meta tag 'clckd' with value '0c55b827446ada040689ccde29552571' is a non-standard, opaque identifier likely used for click-fraud tracking or affiliate session tracking, invisible to end users. (location: page.html:8)
curl https://api.brin.sh/domain/dewafilm.xyzCommon questions teams ask before deciding whether to use this domain in agent workflows.
dewafilm.xyz currently scores 48/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.