context safety score
A score of 24/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 pushes 10 history states and intercepts the browser back button (onpopstate) to force-redirect users to an external campaign URL at backbutton.videobaba.xyz. This traps users and prevents normal navigation. (location: page.html:1613-1631 (also page-text.txt:1573-1589))
hidden content
Client Hints delegation header (delegate-ch) silently forwards detailed browser/device fingerprinting data (ua-bitness, ua-arch, ua-model, ua-platform, ua-platform-version, ua-full-version, ua-full-version-list, ua-mobile) to the third-party ad domain tsyndicate.com without user awareness. (location: page.html:11)
malicious redirect
Third-party ad iframe loaded from mediax.dscgirls.live with affiliate/tracking parameters (affid, oid, source_id) embeds external content that can execute arbitrary redirects or pop-ups outside the site's control. (location: page.html:295)
malicious redirect
Footer iframe from go.xlviiirdr.com (obfuscated domain using Roman numeral-style encoding) loads live-cam content with tracking parameters and targetDomain pointing to hot-india.com. The obfuscated domain name is a common technique to evade blocklists. (location: page.html:1599)
social engineering
Navigation and header links labeled 'AI Porn Video' and 'Live Girls' use affiliate tracking URLs (go.rmshqa.com with hashed campaignId/userId/sourceId parameters) to funnel users to external monetized platforms via deceptive labeling as site content. (location: page.html:93-94)
hidden content
Analytics/tracking script loaded from stats.indianpornempire.com (a third-party domain unrelated to the site) collects visitor behaviour data without disclosure. The script is deferred and domain-tagged to fullhindibfvideo.com. (location: page.html:120)
hidden content
Two ad network scripts loaded from namastedharma.com (NqwU2N3.js and cGQJ7U8.js) use unresolved macros (%subid1%, %subid2%) as tracking parameters, indicating an affiliate/ad network pipeline that may serve malicious ads or track users across sessions. (location: page.html:1604-1605)
hidden content
Script loaded from a.videobaba.xyz (poppy.js) is a popunder/pop-up ad delivery script. Popunder scripts are commonly used to deliver unwanted redirects, scam pages, or malware payloads to users without visible interaction. (location: page.html:1606)
hidden content
Commented-out interstitial ad code referencing a.pemsrv.com (AdProvider) is present in the HTML. While currently disabled, its presence indicates the site has or plans to use intrusive interstitial ad injection that can redirect users. (location: page.html:1607-1612)
social engineering
Domain is only 49 days old (newly registered) but presents itself as established since 2019, claiming the 'largest collection' of content. This fabricated legitimacy is a social engineering tactic to build false trust. (location: metadata.json (domain_age_days:49) + page.html:1587)
curl https://api.brin.sh/domain/fullhindibfvideo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
fullhindibfvideo.com currently scores 24/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.