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
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
JavaScript uses Function constructor for runtime code generation
hidden content
A 1x1 pixel hidden iframe is injected into the page body with visibility:hidden, position:absolute, top:0, left:0. It dynamically creates and executes a script injecting Cloudflare challenge platform code. While this pattern is associated with Cloudflare bot detection, the hidden iframe technique is also used for covert content loading and tracking. (location: page.html:503 — inline script at bottom of body)
malicious redirect
Header banner links to an external domain 'skillhq.online' (target='_blank') that is unrelated to the site's content. This off-domain ad link could redirect users to potentially harmful third-party sites. The destination domain is not a known major ad network. (location: page.html:497 — <a href='https://skillhq.online' target='_blank'>)
hidden content
Third-party script loaded from cdn.tsyndicate.com with spot/session tracking parameters (data-ts-spot, data-ts-session-duration, data-ts-count, data-ts-delay). TSyndicate is a push-notification and ad network associated with adult traffic monetization that can serve pop-unders, redirects, or unwanted subscription prompts to users. (location: page.html:490 — <script src='//cdn.tsyndicate.com/sdk/v1/p.js'>)
social engineering
Site hosts and promotes alleged 'leaked' private sexual videos of named real individuals (e.g., 'congo president daughter julienne sassou sextape leaked', 'Baltasar Ebang Engonga porn Sextapes'). Distribution of non-consensual intimate imagery constitutes a social-engineering and exploitation vector that can be used to coerce or extort victims and deceive users into engaging with illegal content. (location: page-text.txt:1 — video listing titles)
hidden content
Cloudflare challenge script is embedded via a hidden iframe that writes innerHTML containing a base64-encoded timestamp parameter (t='MTc3MjYzNjg0NA=='). This obfuscated parameter encodes session/timing data and the script is injected covertly without user visibility. (location: page.html:503 — iframe innerHTML: window.__CF$cv$params={r:'9d71ca58fde1111c',t:'MTc3MjYzNjg0NA=='})
curl https://api.brin.sh/domain/rahaporn.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
rahaporn.com 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.