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 pushes 10 history states and intercepts the browser back button to force a redirect to backbutton.videobaba.xyz for users arriving from external referrers. This is a classic malicious redirect technique targeting unsuspecting visitors. (location: page.html:759-774 / page-text.txt:508-518)
malicious redirect
Menu link 'Indian Live Sex' routes through a third-party ad redirect server at blazingserver.net/revive with redirect.php, obscuring the true destination behind an opaque redirect chain. (location: page.html:291)
malicious redirect
Mobile ad iframe dynamically injected via JavaScript loads content from go.xlviiirdr.com (obfuscated/nonsensical domain name) with a hardcoded userId token, targeting mobile users with a hidden live-cam iframe inserted before the footer. (location: page.html:754-755)
hidden content
Ad scripts from namastedharma.com (EfgTIy5.js and TlwdAn8.js) are loaded dynamically via JavaScript only after user interaction or a 5-second timeout, making them invisible to static scanners and bypassing ad-blocker detection on initial load. (location: page.html:75-113)
hidden content
Ad iframe from a.vartoken.com is embedded in the sidebar widget with no visible label, loading third-party content in a 302x221 pixel frame whose destination and content are opaque to the user. (location: page.html:506)
obfuscated code
Custom base64 encode/decode functions (b2a, a2b, b64e, b64d) are defined inline and used extensively throughout the page to encode ad-insertion configuration, tracking data, and content fragments, making static analysis of ad payloads and injected content difficult. (location: page-text.txt:563-565 / page.html (inline scripts))
hidden content
Client-side analytics script loaded from stats.indianpornempire.com silently fingerprints visitors using the Plausible-style script with data-domain attribute, sending telemetry to a third-party domain without explicit user consent notice visible on the page. (location: page.html:73)
hidden content
Extensive 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-mobile) are delegated to tsyndicate.com via meta http-equiv delegate-ch, allowing detailed browser and hardware fingerprinting by a third-party ad network without user awareness. (location: page.html:74)
curl https://api.brin.sh/domain/xxxindianstories.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xxxindianstories.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.