context safety score
A score of 33/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 checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Back-button hijacking script pushes 10 history states and intercepts the browser back button to redirect users to 'https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=BFS' — trapping visitors and forcibly redirecting them to a third-party campaign URL when they attempt to navigate away. (location: page.html:1529-1561 and page-text.txt:1222-1231)
malicious redirect
'Live Girls' menu link routes through a tracker/redirect chain via 'https://go.xliirdr.com/?userId=245ca507766e740acb84f0b39e2382497db6cf06625168391b231a62bbb26515&targetDomain=hot-india.com&sourceId=BFS-MENU' — an affiliate redirect URL that obscures the final destination and likely leads to a cam/adult monetization site. (location: page.html:213)
hidden content
A `<meta http-equiv='delegate-ch'>` tag silently delegates Client Hints (UA string, platform, architecture, bitness, model, full version list, mobile status) to the third-party domain 'tsyndicate.com', exfiltrating detailed browser/device fingerprinting data without user awareness. (location: page.html:56)
hidden content
Third-party analytics beacon loaded from 'https://stats.indianpornempire.com/js/script.js' (a non-standard analytics domain outside the site's own domain), collecting visitor data and sending it to an external party without explicit disclosure. (location: page.html:55)
obfuscated code
Custom inline base64 encode/decode functions (b2a, a2b, b64e, b64d) are defined and used to encode ad insertion payloads and tracking data stored in data-attributes and cookies, obfuscating the actual ad content and tracking parameters being injected into the page at runtime. (location: page.html:1663-1665 and page-text.txt:1347-1349)
social engineering
Age verification widget from 'ageverif.com' is configured to bypass itself on error or load failure (ageverifError=loadAds) and falls back to loading ads regardless of verification outcome, subverting its own stated purpose and suggesting the age gate is a cosmetic compliance facade rather than an actual access control. (location: page.html:109-151)
hidden content
Ad scripts from 'blazingserver.net' are injected via jQuery at runtime into the DOM for mobile users only (window.innerWidth < 1023), making them invisible to desktop crawlers and static scanners — a technique used to hide ad activity from automated analysis. (location: page.html:1550-1559)
hidden content
Ad scripts from 'namastedharma.com' (MBVAUE7.js and brkv9c8.js) are loaded with deferred dynamic injection gated behind user interaction or a 5-second safety timeout, allowing the site to serve ads to real users while potentially evading crawlers that do not wait for deferred execution. (location: page.html:109-148 and page.html:1526-1527)
curl https://api.brin.sh/domain/bfvideo.siteCommon questions teams ask before deciding whether to use this domain in agent workflows.
bfvideo.site currently scores 33/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.