context safety score
A score of 44/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
social engineering
Popunder ad script loaded from a.pemsrv.com with zone ID 5719376, configured with ad_trigger_method=3 and ad_frequency settings. This is an aggressive popunder/redirect ad network known for deploying unwanted redirects and deceptive ad overlays that can manipulate users (and AI agents browsing on behalf of users) into unintended navigations. (location: page.html, line 141)
malicious redirect
Third-party ad script loaded from //cdn.tsyndicate.com/sdk/v1/p.js with spot ID '3a2e982a2615473585583d83361835f6'. TSyndicate is a known aggressive ad/redirect network that injects popunders, forced redirects, and malvertising payloads at runtime. The script is loaded async/defer without integrity checks. (location: page.html, line 1098)
malicious redirect
Two separate instances of wpadmngr.com adManager.js loaded (data-admpid 325037 and 325039). This ad manager is associated with intrusive ad injection and potential redirect chains on adult content sites. (location: page.html, lines 143 and 1100)
hidden content
Tag cloud block wrapped inside a <details> element with an empty <summary> tag, making the entire keyword tag cloud (45 SEO keyword tags) visually collapsed/hidden by default from human visitors while remaining fully readable in HTML source. This is a common technique for hiding SEO spam from users while exposing it to crawlers and AI agents. (location: page.html, lines 1029-1073)
hidden content
A keyword-stuffed <h1> element injected near the end of the body (after footer and pagination), well outside normal document flow, containing Arabic and English adult SEO spam terms including brand-name keyword hijacking ('pornhub', 'xnxx', 'youporn'). This content is not part of the visible page layout and appears designed to influence crawlers and AI agents rather than human readers. (location: page.html, line 1096)
brand impersonation
Footer tag cloud and hidden H1 contain explicit references to competing brand names 'pornhub', 'xnxx', and 'youporn' as keyword tags, constituting brand-name hijacking to divert traffic and mislead content-classifying AI agents into associating this domain with established adult platforms. (location: page.html, lines 1033-1036 and line 1096)
social engineering
JavaScript disables right-click context menu (document.oncontextmenu = nocontext) and drag events site-wide via the WP Content Copy Protector plugin. While a common plugin feature, this anti-user-control mechanism combined with aggressive ad networks creates a hostile environment that limits user/agent ability to inspect or exit content. (location: page.html, lines 145-151)
curl https://api.brin.sh/domain/arabic-porn-tube.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
arabic-porn-tube.com currently scores 44/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.