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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Back-button hijacking script pushes 10 history states and intercepts the popstate event to redirect users to an external campaign URL (backbutton.videobaba.xyz) when they attempt to navigate back. This traps users on the site and forces them to an unrelated third-party destination. (location: page.html:1013-1031 and page-text.txt:746-763)
malicious redirect
Navigation menu items labeled 'Tamil Cam Girls' and 'Live Cams' link to blazingserver.net/revive redirect endpoints (zoneid=195, zoneid=214) rather than declared destinations, routing users through an opaque ad-redirect server. (location: page.html:307, 1041-1042)
hidden content
Third-party analytics beacon script loaded from stats.indianpornempire.com silently fingerprints visitors and exfiltrates browsing data to an external domain not disclosed to users. (location: page.html:214)
hidden content
A <meta http-equiv='delegate-ch'> tag delegates browser Client Hints headers (UA string, architecture, bitness, model, platform, full version list, mobile flag) to tsyndicate.com — a third-party ad network — allowing covert device fingerprinting without user awareness. (location: page.html:218)
hidden content
An octoclick-verification meta tag (content='0a0e00ccd32b45dd1afd417ee22b6cd5') registers the site with the Octoclick ad network, enabling hidden ad-serving and tracking integrations not visible in the page UI. (location: page.html:217)
obfuscated code
Inline JavaScript defines custom base64 encode/decode helpers (b2a, a2b, b64e, b64d) and uses them throughout the ad-insertion engine to decode and inject arbitrary HTML/script content at runtime via createContextualFragment, obscuring the actual payloads from static analysis. (location: page.html:1146-1148 and page-text.txt:878-880)
social engineering
An ad unit is disguised as a video thumbnail article inside the regular video listing grid, labeled only with a small 'Ad' badge and a title 'Tiktok for porn - 3sex', designed to deceive users into clicking an advertisement believing it is organic content. (location: page.html:657-671)
social engineering
The site claims all content is 'legally compliant' and 'reviewed before posting to ensure adherence to legal standards' in its homepage description, potentially used to lower user guard regarding the nature of the content and third-party data collection. (location: page.html:974 and page-text.txt:706)
curl https://api.brin.sh/domain/tamilsexvids.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
tamilsexvids.net 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.