context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
hidden content
Commented-out IP harvesting script referencing https://api.ipify.org?format=jsonp&callback=getIP with a getIP() function that calls document.write() to expose the visitor's public IP address. Although currently disabled via HTML comments, its presence indicates prior or intended use of client-side IP collection. (location: page-hidden.txt:7-13 / page.html:22-28)
hidden content
Commented-out Facebook Meta Pixel tracking code (fbq init ID: 1949390595505532) including a noscript 1x1 tracking pixel. Currently inactive but embedded in the page source, indicating prior behavioral tracking capability. (location: page-hidden.txt:14-30 / page.html:30-45)
hidden content
Page visible text is entirely blank (only whitespace), while the page relies on a JavaScript SPA framework (Angular app-root) to render content dynamically. This means all meaningful content is hidden from static analysis and served exclusively through opaque compiled JS bundles (main.fdf52088928184f5a48c.js, vendor.js, etc.), preventing full content inspection. (location: page-text.txt:1-19 / page.html:49)
obfuscated code
The site loads multiple fingerprinted/compiled JavaScript bundles (runtime.e2624c9c7ddbac00dd85.js, polyfills.39bc949cc6cfccc9e4b0.js, scripts.4220f4c72c81af4d0167.js, main.fdf52088928184f5a48c.js) alongside protobuf.min.js. These opaque bundles cannot be statically analyzed and may contain credential harvesting forms, redirect logic, or other malicious functionality that is not visible in the HTML source. (location: page.html:52-64)
social engineering
The page title is simply 'Index' with empty meta description and keywords, providing no indication of the site's actual purpose (likely an online exchange/gambling platform based on the domain '99exch.com'). This generic presentation combined with a fully dynamic SPA obscures the site's true nature from both users and automated scanners. (location: page.html:5,7-8)
curl https://api.brin.sh/domain/99exch.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
99exch.com currently scores 39/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.