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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
All script tags use a non-standard type attribute 'fcc79a09706624c8b000d7d5-text/javascript' and 'fcc79a09706624c8b000d7d5-application/javascript' instead of the standard 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique that defers and wraps script execution, masking the true script type from static analyzers and potentially bypassing content security checks. (location: page.html:16, page.html:815, page.html:821)
obfuscated code
A heavily minified and obfuscated pop-under/popup ad script from 'a.pemsrv.com' and 's.pemsrv.com' (adConfig idzone 5332982) is embedded inline. It implements popMagic with dynamic URL loading, cookie tracking, browser fingerprinting, and event-based popup triggering. The script dynamically loads external ad resources at runtime, concealing the final ad destination from static analysis. (location: page.html:821-846)
malicious redirect
The embedded popMagic ad script (pemsrv.com) is configured to trigger popunders/popups via trigger_method:2 on any click of elements with class 'box'. The ad network (pemsrv.com) is associated with adult ad networks known for aggressive redirect chains, malvertising, and drive-by download campaigns. Users clicking anywhere on the page content boxes can be silently redirected to external destinations. (location: page.html:826-846)
hidden content
Multiple tag URLs in the tag cloud use MD5-hashed slugs (e.g., /tags/e46f5cfbd3c8804d8729de86568ca3c3/, /tags/9933eb6e21bc54077b7d5d17ff9e6fce/) instead of human-readable Arabic text slugs. This obscures the actual content category from both users and automated scanners, potentially hiding categories that would otherwise be blocked by content filters. (location: page.html:693-761)
hidden content
Thumbnail images use a 1x1 transparent GIF as the src placeholder (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) with actual image URLs deferred to data-original and data-webp attributes for lazy loading. While common practice, this technique also bypasses image-based content scanners that analyze src attributes directly. (location: page.html:173, 194, 215 (and throughout))
social engineering
The footer contains a link to an external domain 'sexarab.porn' presented as a sister site ('سكس عرب') with target='_blank', directing users off-site without warning. Cross-site traffic funneling to .porn TLD domains is a common technique in adult traffic networks to distribute users across monetized properties. (location: page.html:798)
curl https://api.brin.sh/domain/sexallarab.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
sexallarab.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.