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
malicious redirect
Back-button hijacking script pushes 10 history states then intercepts popstate to force-redirect external visitors to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=TS, trapping users and redirecting them to an external destination on browser back navigation. (location: page.html:1461-1472 and page.html:1617-1629 (DOMContentLoaded event handler))
malicious redirect
Navigation menu items 'Live sex' and 'Indian Sex Cams' link directly through blazingserver.net redirectAd plugin endpoints (e.g. https://blazingserver.net/revive/www/admin/plugins/redirectAd/redirect.php?zoneid=209 and ?zoneid=208), routing users through an opaque third-party redirect ad system. (location: page.html:265 and page.html:322)
hidden content
The meta http-equiv='delegate-ch' tag delegates extensive browser 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-full-version-list, sec-ch-ua-mobile) to tsyndicate.com, enabling detailed hardware/software fingerprinting of visitors by a third-party ad network without visible disclosure. (location: page.html:60)
hidden content
Visitor's real IP address (38.224.232.228) is embedded directly in the JavaScript app configuration variable exposed in page source, leaking scanner/visitor IP to any third-party scripts that access the global 'app' object. (location: page.html:1534 and page.html:1692 (app-js-extra inline script, user_ip field))
obfuscated code
Custom base64 encode/decode functions (b2a, a2b, b64e, b64d) are embedded inline and used by the ad injection framework (AI plugin) to encode/decode ad block configurations and tracking data at runtime, obscuring the actual ad content and behavior from static analysis. (location: page.html:1540-1542 and page.html:1698-1700)
malicious redirect
Multiple third-party ad scripts loaded from namastedharma.com (//www.namastedharma.com/QaHyPI3.js and //www.namastedharma.com/cMCNdb0.js) with data-spots and data-subid1 tracking parameters. These are external scripts with full DOM access and no integrity checks, capable of performing redirects or injecting content. (location: page.html:1580-1581)
hidden content
Analytics/tracking script loaded from stats.indianpornempire.com (https://stats.indianpornempire.com/js/script.js) silently tracks all visitors. The domain name is distinct from the site domain, functioning as a covert cross-site tracker associated with the Indian Porn Empire ad network. (location: page.html:59)
obfuscated code
Inline IPEA ad loader dynamically creates iframes pointing to https://a.videobaba.xyz/OX/TS/d-ts.php and https://a.vartoken.com/OX/SS/d-ss-v2.php, using obfuscated spot/affID parameters. The ad content loaded into these iframes is entirely controlled by external servers and not inspectable at scan time. (location: page.html:66-120)
curl https://api.brin.sh/domain/tamilscandals3.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tamilscandals3.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.