context safety score
A score of 26/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
JavaScript randomly redirects 20% of non-bot visitors to 'https://onlybokep.net' (a different domain). The redirect logic explicitly checks for known crawler/bot user-agents (googlebot, bingbot, duckduckbot, yandex, crawler, spider) and skips the redirect for them — a classic cloaking technique to evade automated scanners while exposing real users to a potentially malicious destination. (location: page.html:414-433 / page-text.txt:29-48)
obfuscated code
A heavily obfuscated inline script uses decodeURI on a long encoded string, applies a character-position Caesar-cipher transformation (charCodeAt shift by index mod 95), then splits it into indexed substrings and reassembles them at runtime. The resulting payload is never visible in source and is designed to evade static analysis. This pattern is consistent with ad-fraud, traffic manipulation, or drive-by payload delivery. (location: page.html:413 / page-text.txt:28)
hidden content
The obfuscated script block (data-cfasync='false') is injected with the attribute that bypasses Cloudflare's RocketLoader async processing, ensuring it executes immediately and synchronously before other scripts. Combined with bot-detection cloaking, this hides its true behavior from security crawlers. (location: page.html:413)
social engineering
The site presents an age-verification gate ('Are you 18 or older?') implemented via a dismissible JavaScript modal. The 'nope_redirect_url' is empty, meaning clicking 'No' keeps the user on the page or redirects nowhere — the gate is non-functional and serves only as a superficial compliance facade to lower user guard. (location: page.html:402 / page-text.txt:17)
credential harvesting
A login modal collects username and password credentials. The form posts to 'https://onlybokep.com/' (the homepage) rather than a dedicated auth endpoint, and the AJAX URL in the JavaScript config uses plain HTTP ('http://onlybokep.com/wp-admin/admin-ajax.php') instead of HTTPS, potentially exposing credentials in transit. (location: page.html:388,390 / page-text.txt:5)
curl https://api.brin.sh/domain/onlybokep.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
onlybokep.com currently scores 26/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.