context safety score
A score of 40/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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
malicious redirect
The page is served from domain xn--l3cb1eaaa2dkbbb.net (punycode for a Thai adult site) but all canonical URLs, links, login forms, and content resources point to a different domain xn--1-wxfc3gwbi.com. The canonical tag explicitly redirects SEO authority and user navigation to xn--1-wxfc3gwbi.com. The logo image and navigation links split between both domains, indicating the .net domain is a shadow/redirect site funneling traffic to the .com domain. (location: page.html:165 - <link rel="canonical" href="https://xn--1-wxfc3gwbi.com/"> and page.html:336 - logo href pointing to xn--1-wxfc3gwbi.com)
credential harvesting
A login modal form posts credentials (username and password) to https://xn--1-wxfc3gwbi.com/ — a different domain than the one being visited (xn--l3cb1eaaa2dkbbb.net). Users who believe they are logging into the .net site are actually submitting credentials cross-domain to the .com site, which may or may not be controlled by the same actor. A password reset form similarly posts to the foreign domain. (location: page.html:1047 - <form id="wpst_login_form" action="https://xn--1-wxfc3gwbi.com/" method="post"> and page.html:1071)
social engineering
Embedded banner ads link to third-party gambling/lottery and app-download sites (m.appcatcat.com and xn---88-3ml6bqp5a9iqh.net/user/register) using deceptive alt-text ('สล็อตเว็บตรง' = straight slot site, 'แทงหวย' = lottery betting). These ads are embedded within an adult content site to exploit low-guard users and drive registration on gambling/lottery platforms. (location: page.html:374-379 - <a href="https://m.appcatcat.com/th/login"> and <a href="https://xn---88-3ml6bqp5a9iqh.net/user/register">)
hidden content
The site title CSS sets font-size to 0px for .site-title a, making the site title text invisible to users while remaining visible to crawlers and AI agents. This is a SEO cloaking technique that hides the actual brand name from visual display while embedding it in machine-readable contexts. (location: page.html:29 - .site-title a { font-size: 0px; })
brand impersonation
The page at xn--l3cb1eaaa2dkbbb.net presents itself as 'ติดหีหีหีหี.net' but the Open Graph metadata, canonical URL, structured data (JSON-LD), RSS feeds, and all internal navigation links reference a different brand/domain 'ติดหีหีหี.com' (xn--1-wxfc3gwbi.com). The .net domain impersonates the .com domain's brand identity to capture organic traffic and redirect it. (location: page.html:162-182 - title, og:site_name, og:url, canonical, and JSON-LD all referencing xn--1-wxfc3gwbi.com while the served domain is xn--l3cb1eaaa2dkbbb.net)
curl https://api.brin.sh/domain/xn--l3cb1eaaa2dkbbb.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--l3cb1eaaa2dkbbb.net currently scores 40/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.