context safety score
A score of 37/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
malicious redirect
Back-button hijacking script pushes 10 history states then intercepts the back-button popstate event to forcibly redirect non-referring visitors to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=FSK, trapping users and redirecting them to a third-party domain they did not choose to visit. (location: page.html:829-837 and page-text.txt:541-549)
malicious redirect
Navigation menu item 'Live Girls' links through a Revive ad-server redirect URL (https://blazingserver.net/revive/www/delivery/redirect.php?zoneid=340) rather than a direct destination, obfuscating the final landing page and enabling arbitrary redirect chaining. (location: page.html:349)
hidden content
An iframe widget is injected into the page DOM only on mobile screens (window.innerWidth < 1023) via JavaScript innerHTML assignment, making it invisible during standard desktop rendering or static HTML analysis. The iframe sources ads from blazingserver.net and xlviiirdr.com without any visible disclosure. (location: page.html:806-822)
hidden content
Ad script tag from revive.videobaba.xyz is dynamically written via split document.write calls using string concatenation ('<scr'+'ipt') to evade static script-src scanners and content-security-policy analysis. (location: page.html:543-556 and page-text.txt:268-281)
social engineering
The site embeds an age-verification gate (ageverif.com) that, if it fails or errors, automatically falls through to load ad scripts via ageverifError=loadAds and a 5-second safety timeout. This pattern uses the appearance of compliance (age gate) to lower user guard while ensuring ads load regardless of verification outcome. (location: page.html:108-115)
hidden content
Analytics/tracking beacon loaded from stats.indianpornempire.com (third-party domain) via a deferred script tag, collecting visitor telemetry on behalf of an external network (IPE Network) not clearly disclosed to users as a data-sharing arrangement. (location: page.html:73)
hidden content
Client hints (sec-ch-ua, sec-ch-ua-platform-version, sec-ch-ua-full-version-list, etc.) are delegated to tsyndicate.com via http-equiv delegate-ch meta tag, silently sending detailed browser fingerprint data to a third-party ad-tech domain on every subresource request. (location: page.html:75)
curl https://api.brin.sh/domain/freesexkahani.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
freesexkahani.com currently scores 37/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.