context safety score
A score of 37/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)
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site uses a Punycode IDN domain (xn--72c0anj1fqy6jqa7ei.net) that renders as Thai characters visually similar to legitimate brand names (e.g., Pornhub, Xvideos, Brazzers). The page extensively invokes brand names like 'Pornhub', 'Xvideos', 'BRAZZERS', 'BrazzersExxtra', and 'Onlyfans' in titles and metadata to attract traffic under false association with those brands. (location: page.html:26-41, page.html:34, page.html:357, page.html:912 — meta title/description and post titles)
hidden content
The site title H1 element is marked with class 'is-hidden', hiding the full keyword-stuffed site name from visual display while keeping it in the DOM for SEO crawlers and AI agents. This constitutes cloaking — showing different content to bots/crawlers versus human users. (location: page.html:219 — <h1 id='site-title' class='is-hidden'>)
hidden content
The Histats tracker script in the footer uses a homoglyph/lookalike character in the domain 'hístats.com' (with an accented 'í', Unicode U+00ED) instead of the legitimate 'histats.com'. This obfuscates the actual external script source being loaded, potentially evading URL-based security filters. One instance uses the spoofed domain, while a second instance uses the correct domain. (location: page.html:1017 — hs.src = ('//s10.hístats.com/js15_as.js'); and page-text.txt:804)
obfuscated code
A Histats analytics script is injected twice in the footer with a homoglyph domain ('hístats.com' with Unicode accented 'í' character U+00ED instead of plain ASCII 'i'). This technique obfuscates the true script source to evade security scanners and content filters that match on literal domain strings, while dynamically injecting a remote script into the page head or body. (location: page.html:1017 — hs.src = ('//s10.hístats.com/js15_as.js') inside dynamically created script element; also page-text.txt:804)
social engineering
Multiple post titles describe non-consensual or coercive sexual scenarios (e.g., 'ลูกวิปริตจับแม่เย็ดทำเมีย' — son forcing mother; bondage/restraint scenarios in Exclusivesmile post; descriptions of buying sexual services) which can be used to normalize exploitation and manipulate users into believing such content is consensual or freely available, potentially luring vulnerable users. (location: page.html:762 (post-50904), page.html:507 (post-50958), page.html:477 (post-50968) — post title content)
malicious redirect
The footer references an alternate domain 'หนังโป้เด้อ.COM' (a .COM counterpart to the .NET site), directing users to a separate domain. Combined with the IDN Punycode domain obfuscation, this cross-domain promotion could be used to funnel users between sites for traffic monetization, ad fraud, or exposure to malicious third-party ad networks. (location: page.html:988 — footer paragraph text referencing หนังโป้เด้อ.COM)
curl https://api.brin.sh/domain/xn--72c0anj1fqy6jqa7ei.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--72c0anj1fqy6jqa7ei.net currently scores 37/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.