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)
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The scanned URL is xn--72cc3cj1fsbk9jtci.cc (a .cc IDN domain) but all canonical links, og:url, stylesheets, images, and navigation hrefs redirect to ww.xn--72cc3cj1fsbk9jtci.to — a different TLD (.to). The landing page silently proxies/redirects visitors to a separate domain not matching the scanned URL, a common technique to evade blocklists and confuse security scanners. (location: page.html:12-13 (canonical + og:url), page.html:20 (stylesheet src), page.html:36-39 (favicon links))
hidden content
The domain uses an IDN (Internationalized Domain Name) encoded as xn--72cc3cj1fsbk9jtci.cc (Punycode). The actual Unicode rendering is หนังโป๊จ้า.cc, visually masking the true domain from casual inspection. Combined with the redirect to a .to TLD, this obscures the site's true identity and origin in URL bars and security tools. (location: metadata.json:1 (domain field), .brin-context.md:3-4)
social engineering
Multiple content titles explicitly describe non-consensual scenarios (drugging/intoxicating victims — 'มอมเหล้าเมาหลับไม่รู้เรื่อง ลักหลับ', translated: 'drugged drunk asleep without knowing, sleep-assault'), coercion-framed audition scams ('สาวไทยออดิชั่นนางแบบ โดนหลอกเย็ด', translated: 'Thai girl model audition, tricked into sex'), and underage-framed content ('นักเรียน18ปี', 'น้องม.4' — references to students, including Grade 10 equivalent minors). These titles normalize sexual coercion and may be used as social engineering lures targeting vulnerable users. (location: page.html:107, 141-142, 151-153, 156-158, 167, 177, 222; page-text.txt:56, 91, 101, 116)
hidden content
All internal navigation links use percent-encoded Thai Unicode URLs (e.g., /tag/%e0%b9%80%e0%b8%a2%e0%b9%87%e0%b8%94%e0%b8%ab%e0%b8%b5%e0%b9%80%e0%b8%94%e0%b9%87%e0%b8%81/) which decode to explicit content categories. While percent-encoding is standard, the combination with IDN obfuscation and cross-TLD redirect makes destination URLs non-transparent to automated scanning tools and casual users. (location: page.html:82 (menu-item-13971), multiple article href attributes)
curl https://api.brin.sh/domain/xn--72cc3cj1fsbk9jtci.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--72cc3cj1fsbk9jtci.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.