context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Obfuscated document.write with encoded content
brand impersonation
Site xnxx.health fully impersonates XNXX.COM (xnxx.com), a well-known adult platform. It uses the XNXX logo, title, layout, branding, and metadata while operating on a deceptive .health TLD that mimics the legitimate domain. The page declares itself 'XNXX.COM' with canonical references to xnxx.health, not the real xnxx.com. (location: page.html:2, page.html:56, page.html:51 (title, logo img, schema.org name))
malicious redirect
Navigation links for 'Live Cams' and 'Dating' point to third-party redirect/affiliate domains (s.zlinkt.com) rather than the impersonated site's own pages, indicating traffic monetization via deceptive outbound redirects under the guise of the trusted XNXX brand. (location: page.html:87 (href=https://s.zlinkt.com/v1/d.php?z=5603630, href=https://s.zlinkt.com/v1/d.php?z=5421034))
obfuscated code
Two identical large obfuscated JavaScript blocks use URI-encoded strings with a custom character-shift cipher (charCodeAt modulo 95 rotation) to conceal their payload. The scripts are loaded from clickadu.net ad network and the decoded content is not deterministically safe — this pattern is commonly used to evade static analysis and deliver dynamic payloads including pop-unders, redirects, or fingerprinting. (location: page.html:173-176, page-text.txt:122-124 (data-cfasync=false scripts with decodeURI+charCode obfuscation))
hidden content
A Yandex Metrika tracking pixel is placed off-screen using CSS (position:absolute; left:-9999px) to invisibly track visitors without disclosure. This is a covert surveillance mechanism embedded in a brand-impersonation page. (location: page.html:167 (noscript img src=https://mc.yandex.ru/watch/87594356 style=position:absolute; left:-9999px))
hidden content
All script tags use a non-standard type attribute value '2493631e76c3c850e60b13e4-text/javascript' (a Cloudflare Rocket Loader token) which causes browsers to not execute them natively. Cloudflare's rocket-loader.min.js then re-executes them. This indirection obscures script execution from naive static scanners and can be abused to hide malicious script activation behind a CDN layer. (location: page.html:1, page.html:28, page.html:50, page.html:103, page.html:117-121, page.html:177 (type=2493631e76c3c850e60b13e4-text/javascript throughout))
brand impersonation
The page embeds external CDN assets (JS, CSS, favicon, logo, manifest) from cdn.xhaccess.net — a domain that does not belong to the legitimate XNXX.COM infrastructure (xnxx-cdn.com / assets-cdn77.xnxx-cdn.com). This rogue CDN controls all visual branding assets and scripts delivered to users visiting the impersonating site. (location: page.html:1, page.html:5-6, page.html:35-38, page.html:48, page.html:50 (cdn.xhaccess.net references))
social engineering
The page displays a Hindi-language prompt ('यदि उपलब्ध न हो तो यहां क्लिक करें:' — 'If not available, click here:') followed by links to third-party sites (indiaxnxx.net, bokepjepang.gb.net), targeting non-English speaking users with deceptive fallback navigation designed to drive traffic to affiliate or potentially malicious destinations. (location: page.html:102, page-text.txt:51 (network div with Hindi text and outbound links))
malicious redirect
The xv.conf configuration object references an external stats domain (www.tjk-njk.com) and ExoClick ad domain (s.dss29f.com) embedded in page JavaScript configuration, indicating third-party ad and tracking infrastructure that can serve redirect-based malvertising. (location: page.html:49 (xv.conf domains.stats=https://www.tjk-njk.com, dyn.exoclick_domain=s.dss29f.com))
curl https://api.brin.sh/domain/xnxx.healthCommon questions teams ask before deciding whether to use this domain in agent workflows.
xnxx.health currently scores 38/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.