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
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Back-button hijacking script uses history.pushState() in a loop (10 iterations) to poison the browser history stack, then intercepts the popstate event to force-redirect non-referring visitors to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=BCK. This traps users and redirects them to a third-party ad/content network when they attempt to navigate away. (location: page-text.txt:622-664 / page.html inline script (DOMContentLoaded handler))
malicious redirect
Navigation menu contains a link to https://blazingserver.net/revive/www/admin/plugins/redirectAd/redirect.php?zoneid=342 labeled 'Live Girls'. This is an ad-server redirect URL (/redirectAd/redirect.php) that passes visitors through an intermediary redirect to an unknown destination, obscuring the final landing page. (location: page.html:630 / page-text.txt:65)
malicious redirect
A menu item links directly to https://www.dscgirls.live/?oid=4&affid=2&source_id=BCK&sub1=web&sub2=link&sub3=MENU labeled 'Indian Live Sex', which is an affiliate tracking redirect URL embedding affiliate ID and tracking parameters, routing users to a live-cam monetization site. (location: page.html:588)
hidden content
An iframe ad is injected dynamically into a hidden/empty div (#mhead) via JavaScript only on mobile viewports (window.innerWidth < 1023). The iframe loads from https://blazingserver.net/revive/www/delivery/afr.php?zoneid=84 and is not present in the static HTML, making it invisible to standard scrapers and security scanners. (location: page-text.txt:622-646 / page.html inline script)
hidden content
CSS inline style block in page-text.txt (lines 533-553) is rendered as visible text rather than styled content, indicating raw CSS code is leaking into the text extraction layer. While not malicious on its own, it signals the page may contain widget or ad blocks with injected styles not visible to users. (location: page-text.txt:533-553)
obfuscated code
The page includes custom base64 encode/decode functions (b2a, a2b, b64e, b64d) used by the ad-insertion engine (ai_insert_code, ai_check_and_insert_block) to store and execute ad code blobs encoded in data attributes (data-code). This pattern allows arbitrary HTML/JS to be injected at runtime from encoded strings, bypassing static content analysis. (location: page-text.txt:681-724 / page.html inline scripts)
hidden content
Third-party analytics beacon loaded from https://stats.indianpornempire.com/js/script.js via a deferred script tag. This is a cross-site tracking script hosted on a domain unrelated to the site, silently collecting visitor telemetry and user-agent data for a third-party operator. (location: page.html:412)
hidden content
The <meta http-equiv='delegate-ch'> header delegates Client Hints (sec-ch-ua, sec-ch-ua-platform, sec-ch-ua-full-version-list, sec-ch-ua-mobile, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-bitness) to https://tsyndicate.com. This causes the browser to send detailed device and browser fingerprinting data to a third-party ad-tech domain (tsyndicate.com) on every page load without user awareness. (location: page.html:414)
curl https://api.brin.sh/domain/banglachotikahinii.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
banglachotikahinii.com 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.