context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Back-button hijacking script uses history.pushState() in a loop (10 iterations) to trap users, then intercepts the popstate event to force a location.replace() redirect to 'https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=HXS'. This prevents normal browser back navigation and redirects users to an external third-party domain. The script appears twice in the page (head area and footer). (location: page.html:1091-1098 and page.html:1117-1138)
malicious redirect
Third-party ad script loaded from 'blazingserver.net' via an iframe (zoneid=172) and async script tag. The domain 'blazingserver.net' is an ad-serving infrastructure not affiliated with the site; iframes from unvetted ad networks can serve drive-by download payloads or redirect users without consent. (location: page.html:334, page.html:640, page.html:1115)
hidden content
Client hint delegation meta tag delegates detailed 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 the third-party domain 'tsyndicate.com'. This silently exfiltrates device/browser fingerprint data to a third party without user awareness. (location: page.html:5)
hidden content
Analytics/tracking script loaded from 'stats.indianpornempire.com' with a data-domain attribute, enabling cross-site tracking of user behavior. The domain is a third-party tracker not disclosed in any privacy notice visible on the page. (location: page.html:32)
hidden content
Two obfuscated ad scripts loaded from 'namastedharma.com' with randomized filenames ('Xkqlsq5.js' and '0Mcg0B8.js') and data-spots/data-subid parameters. Randomized JS filenames are a common obfuscation technique to evade blocklists; the scripts execute arbitrary code with full DOM access. (location: page.html:1111-1113)
social engineering
Ad units disguised as video thumbnails ('Instagram sexy reels - KamaReels.com') are injected inline among real video items with identical visual styling (duration, view counts, rating badge). The ads use a fake 90% rating and fabricated view count (8.8K) to appear as organic content, deceiving users into clicking affiliate/cam site links. (location: page.html:330-350, page.html:636-656)
social engineering
Navigation menu contains affiliate/referral links to external cam sites (kamareels2.com with ref=MF-HXC, dscgirls.live with affid=19, buzzvideoz.com with ref=MF-HXS) labeled as site navigation items ('सेक्स कैम्स', 'Sex Cams', 'Sexy Girls'), disguising monetized affiliate redirects as internal navigation. (location: page.html:66-68)
curl https://api.brin.sh/domain/hindixxxsite.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hindixxxsite.com currently scores 43/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.