context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
domain spoof risk
domain has spoofing indicators (punycode/confusable/highly synthetic naming)
hidden content
The domain uses a Punycode/IDN encoded hostname (xn--72cm8an6ed3b4dwe6bh.net) that decodes to Thai script (หนังผู้ใหญ่.net). This obfuscates the true nature of the domain from users and security tools that display only the encoded form, and is a known technique to obscure adult/illicit site identity. (location: metadata.json: domain field; page.html: <head> canonical and all href references)
hidden content
A search form in the mobile navigation bar (class 'sfrom') is styled with display:none by default and only shown on screens narrower than 959px. It submits to a different domain (xn--72cm8an6ed3b4dwe6bh.com) rather than the .net domain the page is served from, silently redirecting mobile search queries to an alternate domain. (location: page.html lines 330-334; CSS block lines 96-105)
malicious redirect
The hidden mobile search form (class 'sfrom') submits user search queries to https://xn--72cm8an6ed3b4dwe6bh.com/ (the .com variant), which is a different domain from the canonical site (xn--72cm8an6ed3b4dwe6bh.net). This silently redirects mobile user searches to a separate, unverified domain without disclosure. (location: page.html line 331: <form action='https://xn--72cm8an6ed3b4dwe6bh.com/'>)
hidden content
The Histats analytics script URL uses a lookalike Unicode character in the domain: 'hístats.com' (with an accented í, U+00ED) instead of the legitimate 'histats.com'. This is a homograph/IDN homoglyph technique that causes the browser to load a script from a visually similar but distinct domain, potentially delivering malicious tracking or payload code. (location: page.html lines 3178 and page-text.txt lines 1482: hs.src = ('//s10.hístats.com/js15_as.js'))
social engineering
Multiple video thumbnails and titles describe or depict non-consensual sexual scenarios including rape/coercion (โดนลักหลับจับเย็ดข่มขืน - 'raped while sleeping'), grooming of minors (สาวไทยอายุ17 - 'Thai girl age 17' solicited for sex), and exploitation narratives. These descriptions normalize sexual coercion and could be used to lure or manipulate vulnerable users. (location: page.html lines 1982, 2042; page-text.txt lines 726, 894, 922)
social engineering
Content explicitly references a 17-year-old Thai female being solicited for sex by a foreign man (TukTukPatrol - Oil: 'สาวไทยอายุ17โดนควยฝรั่งเย็ด'). Hosting and presenting child sexual exploitation material framed as entertainment is a form of social engineering that normalizes CSAM and may be used to groom minors. (location: page.html line 1982; page-text.txt line 894)
curl https://api.brin.sh/domain/xn--72cm8an6ed3b4dwe6bh.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--72cm8an6ed3b4dwe6bh.net currently scores 41/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.