context safety score
A score of 43/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site xnxxsex.net uses 'XNXX.COM' prominently in its title, meta description, og:title, og:site_name, and twitter:title tags to impersonate the legitimate XNXX.COM adult content platform. The domain xnxxsex.net is not XNXX.COM but falsely presents itself as the official brand to attract traffic intended for the real site. (location: <title>, <meta name='description'>, og:title, og:site_name, twitter:title tags in page.html)
brand impersonation
The site lists competing adult platform brand names (PORNHUB, REDTUBE, XHAMSTER, XVIDEOS, YOUPORN, BRAZZERS) as internal navigation categories on xnxxsex.net, using these well-known brand names to capture search traffic and deceive users into thinking the site hosts or is affiliated with content from those platforms. (location: Navigation category links in page.html (e.g., /c/pornhub/, /c/redtube/, /c/xhamster/, /c/xvideos/, /c/youporn/, /c/brazzers/))
malicious redirect
An inline script dynamically loads an external script from //kkadverts.com/gopu/sw.js after a 10-second delay (setTimeout of 10000ms). The script also stores a redirect URL in a variable 'golup' pointing to //kkadverts.com/gonow/?go=xnxxsex.net. The 10-second delay is a classic evasion technique to avoid detection by automated scanners. kkadverts.com is an adware/push-notification ad network known for aggressive redirects and unwanted subscription prompts. (location: Inline <script> block at end of <body> in page.html: var golup='//kkadverts.com/gonow/?go=xnxxsex.net';setTimeout(function(){...a.src='//kkadverts.com/gopu/sw.js'...},10000))
hidden content
A JavaScript setTimeout creates a 0x0 pixel image element dynamically with style 'position:absolute;left:-9710px;width:0;height:0', placing it 9710 pixels off-screen to the left and invisible. This is a covert tracking/fingerprinting element hidden from the user and from simple DOM inspection. It is appended to document.body after a 10ms delay. (location: Inline script block 1 in page.html: setTimeout(function(){var y=document.createElement('img');y.style='position:absolute;left:-9710px;width:0;height:0';y.alt='';document.body.appendChild(y)},10))
social engineering
The site is an adult content clone/aggregator (xnxxsex.net) impersonating the well-known XNXX.COM brand, using Arabic-language SEO content and explicit video thumbnails to lure Arabic-speaking users. The site uses push notification subscription prompts (via kkadverts.com sw.js service worker) which are a common social engineering vector to get users to grant persistent notification permissions, enabling ongoing unwanted ad delivery even after leaving the site. (location: page.html: kkadverts.com service worker script load; page-text.txt: Arabic adult content listings)
curl https://api.brin.sh/domain/xnxxsex.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
xnxxsex.net currently scores 43/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.