context safety score
A score of 49/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
malicious redirect
The page at nibba.trade immediately redirects visitors via JavaScript (window.location) through pornhub.ie/search/redirect.php to quickresultsonline.com, a domain-parking/ad-redirect chain. The redirect is conditional on a tracking beacon (tsc.php) returning HTTP 200, indicating coordinated traffic monetization or malicious redirection infrastructure. (location: page.html:12 - window.location assignment inside XMLHttpRequest onreadystatechange)
brand impersonation
The page title and meta description explicitly impersonate 'pornhub' and 'pornhub.ie', presenting nibba.trade as a resource/information site for pornhub while actually being a Sedo domain-parking redirect page. The page falsely claims to be 'your first and best source for information about pornhub'. (location: page.html:1 - <title> and <meta name="description"> tags)
obfuscated code
All redirect URLs are Unicode-escaped (\u003D, \u002D, \u0026, \u00253A, \u00252F, etc.) to obscure the destination domains and query parameters from static analysis. Double URL-encoding is used in the final redirect target (\u00253A = %3A = ':') to further hide the destination quickresultsonline.com. (location: page.html:7-12 - XMLHttpRequest URL and window.location value)
hidden content
The page renders no visible content to the user (no rendered text, no UI elements) — only a 16x16 pixel preloader GIF and JavaScript. All meaningful content (the redirect destination) is hidden inside JavaScript and only executes after a server-side tracking call, making the true behavior invisible to casual inspection or screenshot-based scanners. (location: page.html:5 - <img> preloader and <script> block; page body contains no visible text)
curl https://api.brin.sh/domain/nibba.tradeCommon questions teams ask before deciding whether to use this domain in agent workflows.
nibba.trade currently scores 49/100 with a suspicious 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.