context safety score
A score of 35/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
phishing
Page impersonates PayPal login
malicious redirect
External script loaded from suspicious third-party domain 'jc.peccantdhurna.com' with data-cfasync=false to bypass Cloudflare async filtering. The domain name 'peccantdhurna' is nonsensical/random, a common pattern for malvertising and drive-by redirect networks. Script ID 127683 is a numeric ad/redirect tag. (location: page.html line 1: <script data-cfasync="false" async type="text/javascript" src="//jc.peccantdhurna.com/rnKAfralHoHelJtl0/127683">)
brand impersonation
Site explicitly references and impersonates multiple legitimate Indian OTT/content platforms by name to lure traffic: 'UlluUncut, Xmasti, HiWebxseries, UncutMaza, ixiporn, hdmaals'. Also directly references 'Ullu XXX' and 'Ullu Originals' in navigation and meta description, trading on the Ullu brand to attract users searching for the legitimate platform. (location: page.html line 358 (promo-card text); page.html line 1 (meta description); page-text.txt line 1)
malicious redirect
Navigation menu contains an outbound link to an external domain 'desileak.xyz' (target=_blank) embedded directly in the site's main navigation as 'Desi Sex Video'. This cross-site navigation to an unrelated external domain from the main menu is a pattern used to funnel traffic to potentially malicious or ad-heavy third-party sites. (location: page.html line 358: <a target="_blank" href="https://desileak.xyz/">Desi Sex Video 💋</a>)
hidden content
Multiple JavaScript resources have their MIME type obscured using a Cloudflare Rocket Loader nonce pattern ('dce5e028b87970954c74165c-text/javascript' and 'dce5e028b87970954c74165c-module') as the type attribute, deferring script execution. While this is a Cloudflare feature, it means scripts including the third-party tracker from peccantdhurna.com and Google Tag Manager are deferred/masked from standard script-blocking analysis until Rocket Loader activates them. (location: page.html lines 188, 214, 362, 363: type="dce5e028b87970954c74165c-text/javascript")
hidden content
A 1x1 invisible iframe is injected into the document body via inline JavaScript as part of Cloudflare's challenge platform mechanism. While legitimate in isolation, the pattern (absolute-positioned, zero-border, hidden iframe that dynamically injects scripts) can be abused or mimicked for hidden content delivery. The iframe injects '/cdn-cgi/challenge-platform/scripts/jsd/main.js' via dynamic script creation inside the iframe document. (location: page.html line 364: iframe height=1 width=1 style=position:absolute injected by inline script)
social engineering
Site uses aggressive social proof and urgency language to manipulate users into engagement: claims to be 'loved by fans' of multiple major platforms, offers 'free streaming & download' of premium/paid content, and uses sexually explicit navigation labels with emoji to normalize and encourage visits. The site redistributes premium paid content (Ullu, etc.) for free, which may be used as a lure to harvest ad impressions or redirect users to malicious pages. (location: page.html line 358 (promo-card); page-text.txt line 1 (visible text))
curl https://api.brin.sh/domain/uncutraza.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
uncutraza.com currently scores 35/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.