context safety score
A score of 30/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
1 deceptive links where visible host does not match destination host
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 uses history.pushState() in a loop (10 iterations) to trap the browser history stack, then intercepts the popstate event to force a redirect to 'https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=HBFV' when the user attempts to navigate back. This prevents users from leaving the page normally and redirects them to a third-party ad/monetization endpoint. (location: page.html:1604-1621 (inline <script> in footer); also visible in page-text.txt:1564-1580)
malicious redirect
Third-party ad script loaded from 'blazingserver.net' (//blazingserver.net/revive/www/delivery/asyncjs.php) via a protocol-relative URL. This ad server is embedded inside content thumbnail slots and can inject arbitrary redirects or pop-ups without disclosure. The domain is not the site's primary ad network and uses an ad-serving infrastructure (Revive adserver) that is frequently abused for malvertising. (location: page.html:600, page.html:1085)
hidden content
An interstitial ad block is present in the HTML but wrapped in an HTML comment to disable it: a pemsrv.com ad-provider script and an AdProvider push call are commented out. The structure (<!-- Interstitial --> followed by commented-out script tags) indicates a dormant interstitial ad payload that could be re-enabled server-side or conditionally injected, and was extracted as hidden content by the pre-scan tooling. (location: page.html:1598-1603; page-hidden.txt:1-4)
social engineering
Navigation link labeled 'AI Porn Video' (href: https://www.cmonbae.com/?union_id=MjM1) and 'Live Girls' (href: go.rmshqa.com tracking URL with campaign/user/source IDs) are embedded in the mobile header nav with rel='nofollow' and target='_blank'. These use affiliate/tracking URLs with encoded user and campaign identifiers, designed to funnel users to live-cam and AI-generated adult content sites through social-engineering lures that blend seamlessly into site navigation. (location: page.html:93-94)
malicious redirect
Footer loads two scripts from 'namastedharma.com' (a known adult ad/traffic monetization network): one with data-spot and data-subid1 parameters, and another with unresolved macro placeholders '%subid1%' and '%subid2%' in the data attributes. These scripts can trigger pop-unders, redirects, or traffic arbitrage. Additionally, a 'poppy.js' script is loaded from 'a.videobaba.xyz' which is a known pop-up/pop-under ad delivery script. (location: page.html:1595-1597)
hidden content
The page delegates Client Hints 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 tsyndicate.com via the 'delegate-ch' meta tag. This causes the browser to send detailed device/browser fingerprinting data to a third-party ad syndication domain (tsyndicate.com) on every page load, enabling covert fingerprinting without user awareness. (location: page.html:11)
social engineering
A third-party analytics/tracking script is loaded from 'stats.indianpornempire.com' attributed to a different domain ('fullhindibfvideo.com') via the data-domain attribute. This cross-domain tracking script collects behavioral analytics for an ad empire network entity, not transparently disclosed to users. (location: page.html:120)
curl https://api.brin.sh/domain/hindibfvideo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hindibfvideo.com currently scores 30/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.