context safety score
A score of 22/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
js obfuscation
Obfuscated document.write with encoded content
malicious redirect
Back-button hijacking script pushes 10 history states and intercepts popstate to forcibly redirect users to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=ISS when they attempt to navigate back. This traps users on the site and forces them to an external ad/redirect endpoint. (location: page.html:1124-1131 and page-text.txt:893-900)
malicious redirect
Affiliate tracking links for 'Indian Sex Cams' and 'Cam Girls' route through keitaro.dsccash.com, a third-party affiliate redirect/tracker (e.g., https://keitaro.dsccash.com/thLR7y and https://keitaro.dsccash.com/p8HFSY), which can chain-redirect users to unknown destinations including potentially deceptive cam or subscription sites. (location: page.html:291, 361, 996)
hidden content
The 'Recommended Stories for you' section is rendered with inline style 'display: none' — content is present in the DOM but not visible to users, loaded via a placeholder div. This pattern can be used to inject invisible content or tracking payloads. (location: page.html:834-836)
social engineering
Email subscription form ('ISS Club - Free Erotic Stories') solicits user email addresses with the inducement of free weekly erotic content. The form submits to the site's own backend, but the offer of free content to harvest email addresses is a classic social engineering vector for building mailing lists that may be monetized or abused. (location: page.html:885-914)
hidden content
Client-side HTTP header delegation via meta http-equiv='delegate-ch' sends multiple sec-ch-ua client hint headers (including platform, architecture, model, full-version-list, and mobile status) to tsyndicate.com, exposing detailed browser and device fingerprint data to a third-party ad syndication domain. (location: page.html:67)
hidden content
Third-party analytics/tracking beacon loaded from stats.indianpornempire.com/js/script.js — an owned-network stats domain — collects visitor data outside the primary domain, reducing transparency of data collection practices. (location: page.html:65)
obfuscated code
Custom base64 encode/decode functions (b2a, a2b, b64e, b64d) are defined inline and used throughout the ad insertion framework (AI plugin) to store and execute ad code payloads via atob/btoa. While the AI plugin is a known WordPress plugin, the pattern of storing executable code in base64 within data attributes and decoding it at runtime is a recognized obfuscation vector. (location: page.html:1221-1223 and page-text.txt:988-990)
malicious redirect
Ad iframe content loaded dynamically from blazingserver.net (Revive Adserver) via document.write, with the ad server URL dynamically constructed using location.protocol, current page URL, and referrer passed as parameters. This exfiltrates the user's current URL and referrer to the third-party ad server on every page load. (location: page.html:1086-1097)
curl https://api.brin.sh/domain/indiansexstories3.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
indiansexstories3.com currently scores 22/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.