context safety score
A score of 62/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
Multiple video thumbnail links point to a generic /link.php redirect endpoint (e.g., https://ar.szexvideokingyen.xyz/link.php) instead of direct video pages. This opaque redirect script conceals the final destination and is a classic pattern for traffic monetization redirects, potential malware delivery, or affiliate fraud chains. Users and AI agents clicking these links cannot determine the actual destination before following them. (location: page.html lines 83, 179, 310, 343, 408, 440, 473, 537, 633, 665)
hidden content
A full server-side debug bar (id='dsf') is appended after the closing </body> tag and injected outside the normal document flow. It is rendered with visibility:hidden and display:none by default. The debug output leaks internal server-side file paths (.../projects/rokot/project/model/SecureLink.php), PHP NOTICE errors for 'Undefined index: scheme' and 'host' in SecureLink.php, memory usage, execution timings, and a full profiler/backtrace UI. This information disclosure is useful for attackers and should not be present in production responses served to users. (location: page.html lines 1806-end (after </body>); page-text.txt lines 1915-1937)
hidden content
The debug bar contains embedded base64-encoded image data (data:image/gif;base64,...) inside inline JavaScript. This accounts for the 2 suspicious base64 blobs flagged by Tier 2 analysis. The blobs resolve to small UI icons and are not injections, but their presence inside a post-body debug bar that is hidden from normal view warrants noting. (location: page.html line 1967 (data:image/gif;base64 in debug bar button))
social engineering
The site uses a large network of at least 30 cross-linked sister domains (ar.porno444.com, ar.xxxanalcasero.com, ar.azerisikisme.cyou, ar.fetegoale.top, ar.sekasi.org, etc.) in an h2.friends block styled to look like a navigation/resource section. These affiliate link farms drive traffic across a coordinated adult content network. The .cyou, .top, .click, .casa TLDs are commonly abused by low-reputation operators. An AI agent following these links would be directed to a web of potentially unsafe third-party domains. (location: page.html lines 1410-1432)
hidden content
User-agent differential ratio of 0.16 was flagged by Tier 2 scanning, indicating the server may serve different content depending on the requesting client. Combined with the opaque /link.php redirect endpoints, this suggests the site may deliver different (potentially more malicious) destinations to headless browsers, bots, or AI agents versus regular browsers. (location: .brin-context.md (user-agent diff ratio: 0.16); page.html /link.php hrefs)
curl https://api.brin.sh/domain/ar.szexvideokingyen.xyzCommon questions teams ask before deciding whether to use this domain in agent workflows.
ar.szexvideokingyen.xyz currently scores 62/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.