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)
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The scanned URL is xn--72ca1b0f3bvd2c.com but all canonical links, og:url, assets, and internal navigation point exclusively to xn--72caa3cygoc0d9c.com. The served page is effectively from a different domain than the one scanned, indicating a redirect or domain-substitution that delivers content from a separate punycode domain. Users and agents navigating to the scanned domain land on a different domain's content without a clear redirect notice. (location: page.html:10 (canonical href), page.html:3 (asset preload), metadata.json (url field vs. page canonical))
social engineering
Multiple advertisement banners link to third-party gambling/casino sites (https://ibit.ly/vip168sa and https://macau432.com/register) using shortened/obfuscated URLs embedded within an adult content site. This placement exploits the captive audience of an adult site to funnel users to gambling registration pages, a recognized social-engineering pattern for financial harm. (location: page.html:608-612 (dac-grid banner ads))
hidden content
Inline CSS comment blocks (CDATA-wrapped styles) and raw CSS text are rendered into the visible page-text.txt output (e.g., '.ads-section--banner[data-section=banner_homepage]' appearing inline in visible text), indicating that stylesheet content leaked into the text layer. While likely a rendering artifact, it can obscure actual page content from scrapers and AI agents parsing the text representation. (location: page-text.txt:60-65 (inline CSS in text layer))
malicious redirect
An ibit.ly shortened URL (https://ibit.ly/vip168sa) is used in an advertisement anchor tag with rel='nofollow sponsored external noopener noreferrer'. Link shorteners mask the final destination, preventing agents and users from knowing where they will be redirected before clicking. (location: page.html:608 (ibit.ly banner ad href))
curl https://api.brin.sh/domain/xn--72ca1b0f3bvd2c.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--72ca1b0f3bvd2c.com 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.