context safety score
A score of 38/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
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
obfuscated code
Two identical large obfuscated inline scripts use a custom character-rotation cipher (decodeURI + per-character Caesar shift by index) to decode and execute payload at runtime. The decoded string is split into segments and assembled into URLs, function names, and logic that cannot be statically analyzed. This pattern is strongly associated with ad-fraud, malicious redirect, and drive-by-download infrastructure. (location: page.html:120 and page.html:122 (duplicate <script data-cfasync='false'> blocks))
malicious redirect
External script loaded from third-party domain 'salutetutortwiddling.com' (//salutetutortwiddling.com/on.js) with an onload/onerror callback tied to the obfuscated code ('rstbnag(15)'). This domain name is a nonsense compound word — a hallmark of auto-generated malvertising/redirect network domains. The script is loaded asynchronously and can trigger arbitrary redirects or pop-unders. (location: page.html:121)
malicious redirect
Second external script loaded from 'broadsidedaisysanta.com' (//broadsidedaisysanta.com/in.js) with onload/onerror callback 'ecltehxg(17)'. Same pattern as above — nonsense-compound domain name characteristic of malvertising redirect networks. Both domains follow the same obfuscated callback pattern suggesting coordinated malvertising infrastructure. (location: page.html:123)
hidden content
A commented-out script tag references 'https://www.vipads.live/vn/AFBFA8B2-15BA-669-34-5FC0A19B09E4.blpha' — a non-standard .blpha extension on a domain named 'vipads.live'. This appears to be a dormant or toggled ad/redirect payload that can be re-enabled trivially, and the .blpha extension is not a recognized web resource type, suggesting obfuscated payload delivery. (location: page.html:124)
brand impersonation
The site is hosted at clipsexsub3x.net but presents itself throughout as 'HAYSEX.NET' — in the title, og:site_name, logo alt text, schema.org structured data, and footer text. The site explicitly states it is the 'successor' to haysex.net and haysex3x.com, impersonating an established brand on a different domain to inherit user trust and search engine authority. (location: page.html:24,31,34,38 and page-text.txt:1228-1231)
social engineering
Multiple video listings are labeled as 'leaked' private content of named real individuals (e.g., 'Clip Sex Bình Nhi 2k6 Tư Liệu Bí Mật Trên Điện Thoại Bạn Trai', 'Lê Ngọc Thi 2k6', 'Clip Sex Bùi Trúc Quyên'), exploiting curiosity and voyeurism to lure users into clicking, which may trigger the malvertising redirect scripts. (location: page.html:623-643, page-text.txt:457,1078)
credential harvesting
A login modal is embedded in the page with username and password fields posting to the site (WordPress admin-ajax.php endpoint). While standard for WordPress, the combination of brand impersonation (clipsexsub3x.net posing as haysex.net) and the adult content lure creates a context where users may submit credentials believing they are logging into a different, established site. (location: page-text.txt:1289-1334, page.html (login modal))
curl https://api.brin.sh/domain/clipsexsub3x.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
clipsexsub3x.net currently scores 38/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.