context safety score
A score of 38/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
malicious redirect
Back-button hijacking script pushes 10 history states and intercepts popstate to force-redirect users to 'https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=IBF' when the back button is pressed. This traps users and redirects them to a third-party affiliate/ad destination against their intent. (location: page.html:1641-1648 and page.html:1666-1686)
malicious redirect
Navigation link labeled 'Live Girls' points to 'https://blazingserver.net/revive/www/admin/plugins/redirectAd/redirect.php?zoneid=348', which is an opaque ad-network redirect through blazingserver.net. The link label is deceptive and routes through a redirect endpoint that could forward users to arbitrary destinations. (location: page.html:97)
hidden content
Client Hints (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) are delegated to the third-party domain 'tsyndicate.com' via a delegate-ch meta header. This silently sends detailed browser and platform fingerprint data to a third-party ad/tracking domain without user awareness. (location: page.html:15)
hidden content
Two deferred scripts are loaded from 'https://www.namastedharma.com' (tZxCiz4.js and PSfrwk9.js) with spot/subid tracking parameters. These scripts are not disclosed to users and load from an opaque third-party domain associated with ad injection and popunder networks; their behavior is not visible in the page content. (location: page.html:1664-1665)
hidden content
An analytics script ('https://stats.indianpornempire.com/js/script.js') is loaded deferred with a data-domain attribute, silently sending telemetry to a third-party domain (indianpornempire.com) cross-site without disclosure. (location: page.html:32)
social engineering
Content description promotes 'leaked MMS' (likai MMS) and 'hidden/leaked videos' of real individuals, including a video explicitly titled as a leaked MMS of a named public figure ('payal gaming mms' - a YouTube creator). This constitutes non-consensual intimate imagery framing designed to lure users and exploit the reputation of real individuals. (location: page.html:535-563, page-text.txt:513)
social engineering
Site description text promises an upcoming 'leaked MMS category' to drive return visits, using engagement bait framing around non-consensual content distribution as a retention mechanism. (location: page.html:1654, page-text.txt:1620)
curl https://api.brin.sh/domain/indianbfvideos.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
indianbfvideos.com currently scores 38/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.