context safety score
A score of 38/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
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Pop-under script loads external JS from 'chubbyexemplaryhardiness.com/on.js' and opens a new window to 'official-permit.com' after tracking user page counts via localStorage. This is a deliberate pop-under ad redirect mechanism triggered after 4-7 page views, designed to send users to unknown third-party destinations without consent. (location: page.html:753-833, page-text.txt:540-620)
obfuscated code
Two identical large obfuscated JavaScript blocks using decodeURI on a heavily percent-encoded string, combined with a character-shifting cipher (charCode-based Caesar-style rotation modulo 95), then split by computed indices. The decoded payload dynamically constructs URLs, window/document API calls, and ad network references. The code is intentionally obfuscated to hide its true behavior from scanners and analysts. (location: page.html:741-746, page.html:746-747)
malicious redirect
External ad script loaded from 'earmuffpostnasalrisotto.com/bn.js' — a nonsense-word domain typical of ad fraud and malvertising networks. No legitimate CDN or analytics provider uses such domain naming. Loaded with data-cfasync=false to bypass Cloudflare security scanning. (location: page.html:742)
malicious redirect
External ad script loaded from 'deductgreedyheadroom.com/in.js' — another nonsense-word domain consistent with malvertising infrastructure. Also loaded with data-cfasync=false to bypass Cloudflare scanning. (location: page.html:747)
social engineering
The site operates under the brand 'Drbokep' on domain 'drbokep.page' but serves logo assets and favicon from a different domain 'drbokep.cv', indicating cross-domain brand fragmentation or a domain migration that creates confusion about the site's true identity. Footer also references 'Powered by Drbokep.xyz', a third distinct domain, further obscuring the true operator. (location: page.html:10, page.html:220, page.html:720, page.html:726)
credential harvesting
Registration and login forms (username, email, password) are embedded in a modal that POSTs to 'https://drbokep.page/' — an adult piracy site with obfuscated ad scripts and cross-domain brand inconsistencies. Users registering on this site surrender credentials to an operator whose infrastructure includes multiple obfuscated redirect scripts and third-party malvertising loaders. (location: page.html:856-896)
hidden content
LiteSpeed referrer-spoofing script executes before page load to override document.referrer from sessionStorage, allowing the site to manipulate traffic source analytics and bypass referrer-based security checks or content policies. (location: page.html:5)
social engineering
The pop-under trigger system uses localStorage to track user page views and timing ('pageCount', 'pop1LastTime', 'pop2Pages') to delay and pace redirect/popup delivery, making the malicious redirects appear less suspicious by not triggering immediately on first visit. (location: page.html:761-833)
curl https://api.brin.sh/domain/drbokep.pageCommon questions teams ask before deciding whether to use this domain in agent workflows.
drbokep.page currently scores 38/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.