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
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
malicious redirect
Back-button hijacking script pushes 10 history states and intercepts the popstate event to redirect users to 'https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=HCV' when they attempt to navigate back. This traps users on the site and redirects them to a third-party affiliate URL against their intent. (location: page.html:1557-1573 (and duplicated at page-text.txt:1523-1538))
malicious redirect
Navigation menu link labeled 'Live Girls' uses an obfuscated affiliate tracking URL via go.rmshqa.com with encoded campaignId and userId parameters, obscuring the true destination from users and AI agents. (location: page.html:91)
malicious redirect
Navigation menu link labeled 'Sex Reels' redirects through kamareels2.com with affiliate tracking parameters (ref=MF-HCV, utm_medium, utm_source), masking the final destination. (location: page.html:90)
social engineering
Site description text uses persuasive urgency and social proof language ('Join 1M+ fans', 'Fresh drops daily', 'No sign-up') to manipulate users into consuming content and clicking affiliate links, consistent with traffic monetization social engineering. (location: page.html:1514 / page-text.txt:1479)
hidden content
Client-hint delegation meta tag delegates sensitive browser fingerprinting headers (sec-ch-ua, sec-ch-ua-bitness, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-platform-version, sec-ch-ua-full-version, sec-ch-ua-full-version-list, sec-ch-ua-mobile) to third-party domain tsyndicate.com, allowing covert device fingerprinting without user awareness. (location: page.html:5)
hidden content
Third-party analytics script loaded from stats.indianpornempire.com tracks user visits via Plausible-style analytics, sending domain and browsing data to a third-party network domain not disclosed to users. (location: page.html:33)
hidden content
Two ad scripts loaded from namastedharma.com (inpage ASG and interstitial+popunder ASG) serve popunder and interstitial ads. Popunder ads open hidden browser windows behind the current window, a classic technique for covert ad delivery. (location: page.html:1553-1555)
hidden content
Ad slot served via blazingserver.net Revive ad server (asyncjs.php) injected inside video thumbnail list items labeled 'AD', loading third-party ad code from an external server with no content security policy restrictions. (location: page.html:422 and page.html:877)
social engineering
Back-button redirect script contains randomized domain check ('Math.random() < 0.3 ? surprise.com : hindichudaivideos.com') to selectively bypass the redirect check approximately 70% of the time, indicating deliberate obfuscation of redirect behavior to evade detection. (location: page.html:1562)
curl https://api.brin.sh/domain/hindichudaivideos.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hindichudaivideos.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.