context safety score
A score of 30/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 the popstate event to forcibly redirect users to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=TSZ — an external third-party redirect service. Triggered for any visitor not arriving from tamilsexzone itself, trapping users in a navigation loop. (location: page.html:837-855 (inline script), page-text.txt:595-612)
malicious redirect
Third-party ad script dynamically injected from https://www.namastedharma.com/ATByhs5.js and https://www.namastedharma.com/iIG0dX4.js via an inline loader. These are obfuscated ad-network scripts loaded after age-gate interaction, with no integrity checks (no SRI), posing a risk of drive-by redirect or malvertising payloads. (location: page.html:196-235 (inline loadAds script))
malicious redirect
Ad iframe loaded from https://blazingserver.net/revive/www/delivery/afr.php?zoneid=446 embedded in page header with allow='autoplay'. Cross-origin ad iframe from an unverified ad server; the corresponding click-through also routes through blazingserver.net, a non-transparent ad intermediary. (location: page.html:283)
hidden content
A <link rel='preconnect'> to https://www.bollyocean.com/ is present in the page head. This silently pre-connects the browser to an external adult domain not visible to the user, leaking browser fingerprint and IP to a third party without disclosure. (location: page.html:145)
hidden content
Client hint delegation header delegates detailed browser/device metadata (sec-ch-ua, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-full-version-list, sec-ch-ua-mobile, sec-ch-ua-bitness) to https://tsyndicate.com — a third-party ad/tracking network — without user awareness. This silently exposes granular device fingerprint data to an external party. (location: page.html:195 (meta http-equiv='delegate-ch'))
hidden content
Analytics beacon loaded from https://stats.indianpornempire.com/js/script.js using a defer script tag. This is a first-party-branded but third-party-hosted analytics tracker that silently reports page visits to indianpornempire.com, a separate adult network domain, without explicit user consent notice on the page. (location: page.html:192)
obfuscated code
Custom base64 encode/decode functions (b2a, a2b, b64e, b64d) are defined inline and used throughout the ad-insertion framework to encode/decode ad block data and tracking attributes at runtime. This obscures ad injection targets, tracking payloads, and click-handler logic from static analysis. (location: page.html:970-973 (inline script), page-text.txt:728-730)
social engineering
An 'AI Porn Video' menu item in the mobile navigation links to https://www.cmonbae.com/?union_id=MTE3 via an affiliate/union tracking parameter. This uses the 'AI' label as an engagement hook to drive affiliate traffic clicks, misrepresenting AI as a content feature. (location: page.html:867)
hidden content
Data trailer attribute for video article post-26427 contains the same MP4 URL repeated 7 consecutive times concatenated into a single malformed URL string. This anomalous data attribute duplication is inconsistent with normal CMS output and may indicate template injection or data-attribute stuffing. (location: page.html:547 (data-trailer attribute of article post-26427))
curl https://api.brin.sh/domain/tamilsexzone.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tamilsexzone.com currently scores 30/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.