context safety score
A score of 44/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)
brand impersonation
The domain xn--l3cg7a8a0cwa3f.cc is a punycode-encoded internationalized domain name that decodes to a Thai-script domain impersonating 'ดูหีไทย.com' (a known adult content brand). The og:description and schema.org description explicitly reference 'ดูหีไทย.CoM' while the actual domain is the .cc punycode variant, indicating brand impersonation of the original .com site to siphon its traffic. (location: metadata.json domain field; page.html <meta property='og:description'> line 16; schema.org JSON-LD line 126)
hidden content
The page title and site logo reference 'Retro Dazle Night Club Logo' in favicon/icon filenames (cropped-Retro-Dazle-Night-Club-Logo-*.webp), which is entirely unrelated to the adult content site presented. This suggests a possible cloaking technique where the underlying WordPress installation was repurposed from a nightclub site, potentially to evade detection or retain a prior trusted domain reputation. (location: page.html lines 7-10, 41-44)
social engineering
Multiple video titles describe scenarios involving deception, coercion, and non-consensual acts framed as entertainment (e.g., 'virgin ปลอมแกล้งร้องไห้หลอกเย็ด' meaning 'fake virgin pretending to cry to trick into sex', 'Slut Hunt' series with descriptions of mouth being taped shut). These social engineering narratives normalize manipulation and coercion tactics. (location: page.html lines 238, 537; page-text.txt lines 179, 479)
malicious redirect
Video embed URLs point to an external third-party CDN domain 'ezycdn.stream' (e.g., embedUrl: 'https://ezycdn.stream/play.php?v=3ortrpfv'). This external player domain is unknown/unverified and could serve malicious redirects, drive-by downloads, or exploit kits when users attempt to play embedded videos. (location: page.html line 126 (schema.org JSON-LD embedUrl fields))
hidden content
Third-party analytics tracker Histats.com (s10.histats.com/js15_as.js) is dynamically injected via JavaScript into either the head or body element. Histats is a known low-reputation tracker sometimes used to fingerprint users and aggregate behavioral data without clear consent disclosure. The script is loaded asynchronously and not surfaced in visible page content. (location: page.html lines 742-750; page-text.txt lines 683-691)
curl https://api.brin.sh/domain/xn--l3cg7a8a0cwa3f.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--l3cg7a8a0cwa3f.cc currently scores 44/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.