context safety score
A score of 45/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
A third-party smart-pop/ad script is loaded from go.tscprts.com (SCSpotScript), a known ad-redirect and popunder network domain. This script dynamically injects content and can redirect users to phishing, malware, or scam pages without user interaction. (location: page.html:901-905, script src=https://go.tscprts.com/smartpop/fcd5edc7...)
malicious redirect
The page prominently links users to https://91porn.cyou as the 'latest address release page', directing traffic to an external domain that serves as a domain-hopping relay for a piracy/adult site ecosystem often used to evade takedowns and funnel users through ad/malware networks. (location: page.html:81, href=https://91porn.cyou)
social engineering
The page uses urgency and trust-building language ('收藏最新地址发布页' — 'Bookmark the latest address release page') to encourage users to follow and bookmark external redirect links, a classic social engineering technique to maintain persistent user access through domain changes and ad-network funnels. (location: page.html:81, page-text.txt:40)
hidden content
A hidden 1x1 pixel iframe is injected via an obfuscated Cloudflare challenge script at the bottom of the page body. The iframe is positioned at top:0, left:0 with visibility:hidden and executes a dynamically created script tag inside it. While potentially a Cloudflare bot-detection mechanism, this pattern is also used for hidden tracking, credential harvesting, and drive-by exploit delivery. (location: page.html:920, inline script injecting hidden iframe with dynamic script execution)
obfuscated code
The Cloudflare challenge script at the end of the body uses a self-invoking obfuscated function that creates a hidden iframe, injects a dynamic script element inside it referencing '/cdn-cgi/challenge-platform/scripts/jsd/main.js', and passes encoded parameters (base64: MTc3MjYzMzM2NA==). The code structure deliberately obscures its behavior and bypasses normal script-loading visibility. (location: page.html:920, inline IIFE script block)
hidden content
Yandex Metrika tracking pixel is rendered as a hidden image (position:absolute; left:-9999px) via a noscript tag, enabling covert tracking of users who have JavaScript disabled. Combined with webvisor:true and clickmap:true options, this constitutes comprehensive covert behavioral surveillance. (location: page.html:36, noscript img src=https://mc.yandex.ru/watch/105865337)
curl https://api.brin.sh/domain/hsex.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
hsex.tv currently scores 45/100 with a suspicious verdict and medium 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.