context safety score
A score of 78/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
hidden content
A full server-side debug bar ("darkside debug") is rendered in the live HTML response after the closing </html> tag. It exposes internal server-side file paths (e.g., .../projects/rokot/project/model/SecureLink.php Line:101), PHP NOTICE errors for 'Undefined index: scheme' and 'Undefined index: host', memory usage, and execution timing. This information disclosure aids attackers in mapping the server architecture and identifying exploitable code paths. (location: page.html lines 1136-1483 (<!-- Begin Debug --> block))
hidden content
The debug bar div (#dsf) and its child elements (profiler, errors panel) are rendered with visibility:hidden and display:none, making them invisible to normal users but fully present in the DOM and readable by automated agents, scrapers, or AI crawlers. The hidden content includes internal PHP error messages and server file paths. (location: page.html lines 1279-1306, page-text.txt lines 1111-1275)
malicious redirect
Multiple video thumbnail links (at least 8 out of ~35 articles) use a generic opaque redirect endpoint '/link.php' (https://ar.reifensex.org/link.php) rather than linking directly to content pages. This pattern is characteristic of affiliate traffic laundering or redirect chains to third-party destinations unknown at parse time. The destination of link.php is not disclosed in the HTML. (location: page.html lines 56, 89, 156, 189, 222, 238, 254, 302, 334, 366)
hidden content
One video article renders a raw HTTP URL (http://vs9.videosrc.net/1/18/18e) inside a <span> element that is styled as a video duration timestamp display. This is an anomalous injection of a plaintext third-party URL into a UI element not intended to display URLs, which could serve as a covert off-domain reference or tracking beacon path embedded in visible content. (location: page.html line 109, page-text.txt line 83)
hidden content
The page uses a <meta name='referrer' content='unsafe-url'> tag, which instructs the browser to send the full URL (including query strings) as the Referer header to all third-party destinations. Combined with the link.php redirect pattern and external image/media hosts, this enables cross-site referrer leakage of the user's full browsing URL to unknown third parties. (location: page.html line 9)
curl https://api.brin.sh/domain/ar.reifensex.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
ar.reifensex.org currently scores 78/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.