context safety score
A score of 79/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
Multiple video thumbnail links use a generic redirect endpoint '/link.php' instead of direct video URLs, funneling clicks through an untracked redirect handler that could forward users to malicious or unwanted destinations. (location: page.html: lines 62, 74, 99, 111, 125, 131, 137 and numerous others — href='https://ar.pizdebatrane.com/link.php')
hidden content
Several video duration fields contain raw external CDN URLs (e.g. 'http://vs3.videosrc.net/8/83/835', 'http://vs9.videosrc.net/0/03/036', 'http://vs6.videosrc.net/e/e9/e9f') rendered as visible text inside <span> elements meant to display video lengths. These appear to be data-injection artifacts or poorly sanitized backend values leaking internal resource paths. (location: page.html: lines 82, 120, 127; page-text.txt: lines 58, 96, 103)
social engineering
The site aggressively keyword-stuffs Arabic-language search terms related to incest ('محارم'), family members ('امهات', 'اخوات', 'الام'), and minors ('المراهقين', 'عارية المراهقين', 'في سن المراهقة') across titles, tags, category labels, and the tag cloud to maximize organic search reach and lure Arabic-speaking users searching for potentially illegal content. The tag cloud lists 'اخ يغتصب اخته مترجم عربي' (brother rapes sister, translated Arabic) as a navigable tag with 28 associated videos. (location: page.html: lines 47, 62-346; page-text.txt: lines 23, 861)
social engineering
The header contains a prompt urging users to bookmark the site due to 'regular updates' ('المرجعية لنا بسبب تحديثات منتظمة'), a classic retention tactic used on adult content aggregators to build habitual return traffic. (location: page.html: line 30; page-text.txt: line 6)
brand impersonation
Video titles and tags prominently reference well-known legitimate adult brands (BangBros, Brazzers, PornHD, VivThomas, MyFamilyPies, Lifeselector, RealityKings, BLACKED, BLACKEDRAW, Baeb, ClubTug) alongside the site's own redirect links, implying affiliation or hosting of their content without authorization. This constitutes brand impersonation to attract traffic. (location: page.html: lines 105, 203, 239, 257, 299, 311, 317, 323 and many others; page-text.txt: lines 82, 180, 288, 294, 300, 546)
curl https://api.brin.sh/domain/ar.pizdebatrane.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ar.pizdebatrane.com currently scores 79/100 with a caution verdict and medium 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.