context safety score
A score of 59/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
hidden content
A full server-side debug bar (darkside/dsf debugger) is rendered after the closing </html> tag and hidden via CSS/JS visibility:hidden. It exposes internal server 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 (2.38 Mb / 2.57 Mb), and execution time. This information leakage assists attackers in fingerprinting the backend stack and directory structure. (location: page.html:1150-1320 (<!-- Begin Debug --> block after </html>))
hidden content
The debug bar elements (dsf_profiler, dsf_errors, dsf_backtrace) are initialized as visibility:hidden and display:none but remain fully present in the DOM with sensitive server-side file paths and error details. The user-agent diff ratio of 0.16 flagged in Tier 2 is consistent with this debug content being conditionally served or rendered differently to different clients. (location: page.html:1293-1320, page-hidden.txt:1-4)
malicious redirect
Multiple video thumbnail links point to https://ar.jolokawek.com/link.php — an opaque redirect endpoint with no visible destination. This pattern (at least 10 article links all pointing to the same /link.php) strongly indicates a traffic monetization redirect chain or affiliate redirect that may route users through malicious ad networks, malware landing pages, or affiliate fraud infrastructure. The destination of /link.php is unknown and cannot be verified from the HTML alone. (location: page.html:56,89,172,189,205,222,238,270,318,334 (href="https://ar.jolokawek.com/link.php"))
hidden content
The <meta name="referrer" content="unsafe-url"> tag is set, causing the full URL (including any query parameters with session tokens or tracking data) to be sent as the Referer header to all external destinations, including the /link.php redirect targets and external affiliate domains. This facilitates user tracking and potential credential/session leakage across the affiliate network. (location: page.html:9)
social engineering
The footer section (lines 1089-1102) contains a dense network of 20 external affiliate/partner adult sites (ar.seksaseksi.com, ar.neukenfilm.net, ar.giaothao.com, ar.niwerat.com, ar.filmikiostrysex.cyou, ar.nutikuw.com, ar.pornofilmekostenlos.org, pl.phimsecnhatban.com, ar.pornophotowomans.com, ar.videopornodivecchie.com, ar.seksabipi.com, ar.phimditnhau.casa, ar.porrfilmsvensk.com, ar.videosxxxmamas.com, ar.baberas.com, ar.madurasamateur.com, ar.fetegoale.top, ar.seratea.com, ar.meisjeneuken.net, ar.nlsexfilms.net) styled as simple text links with minimal visual presentation. This link farm pattern is used to drive SEO traffic and funnel users to potentially unsafe third-party domains, some of which use suspicious TLDs (.cyou, .casa, .top). (location: page.html:1089-1102)
hidden content
Two suspicious base64 blobs flagged by Tier 2 analysis are confirmed present: inline base64-encoded GIF images embedded directly in the debug bar icon buttons (data:image/gif;base64,R0lGODlh...). While these specific blobs decode to small UI icons (16x16 gif images for the debugger toolbar), their presence as inline data URIs inside a hidden debug block that is served to end-users represents unnecessary data exposure and confirms the debug bar is live in production. (location: page.html:1307,1310 (data:image/gif;base64 in debug bar anchor tags))
curl https://api.brin.sh/domain/ar.jolokawek.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ar.jolokawek.com currently scores 59/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.