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
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
Large heavily obfuscated JavaScript block in the <head> uses Caesar-cipher-like character rotation over a long encoded string, dynamic string reconstruction via charCode arithmetic, and runtime eval-style execution. The decoded payload builds URLs and injects scripts dynamically, concealing its true behavior from static analysis. (location: page.html:19 (inline <script> block starting with !function(){"use strict";const t=Date...))
malicious redirect
External script loaded from third-party domain 'bartererfaxtingling.com' (//bartererfaxtingling.com/bn.js). This domain name is characteristic of ad-fraud or malicious ad-network infrastructure and is not a recognized legitimate CDN. The script is loaded with data-cfasync="false" (bypasses Cloudflare scraping shield) and has onerror/onload callbacks referencing the obfuscated xzkrt() function, indicating it is wired into the obfuscated code's redirect/tracking logic. (location: page.html:20 (<script data-cfasync="false" ... src="//bartererfaxtingling.com/bn.js">))
malicious redirect
External ad script loaded from 'js.mbidadm.com' (data-admpid="235087"). This is a third-party ad network script injected into the page body. Such scripts are frequently used to serve pop-unders, forced redirects, or malvertising payloads to visitors, particularly on adult content sites. (location: page.html:46 (<script async src="https://js.mbidadm.com/static/scripts.js" data-admpid="235087">))
hidden content
One tag link uses an MD5 hash string as the URL slug instead of a human-readable tag name: href="/tags/287c31b818d68513b293503b257c60a4/" with display text 'سكس ورعان'. This pattern of using a hash-based path for a visible tag is anomalous and may be used to obscure the true destination or to evade URL-based content filters while routing to specific content. (location: page.html:663 (<a href="https://www.sexlilarab.com/tags/287c31b818d68513b293503b257c60a4/">))
obfuscated code
The obfuscated script reconstructs and calls a function named 'xzkrt' which is referenced in the onerror/onload handlers of the external bn.js script tag. This coupling between the obfuscated bootstrap code and the external malicious-domain script suggests coordinated payload delivery that is intentionally hidden from code review. (location: page.html:19-20 (xzkrt function defined in obfuscated block, called from bn.js handlers))
curl https://api.brin.sh/domain/sexlilarab.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
sexlilarab.com 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.