context safety score
A score of 32/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
brand impersonation
The page title and meta describe 'Omnidex - AI-driven SSP' (Supply-Side Platform for adtech), but the visible page content and forms are entirely about payment processing ('Send Payment', 'Request Payment', 'Bank Name', 'Amount', 'Fast Payment', 'Powering Secure & Seamless Transactions'). The domain omni-dex.io uses a hyphenated variant resembling legitimate 'OmniDEX' or similar fintech/adtech brands, while the actual content pivots to financial transactions — a classic brand impersonation pattern. (location: page.html: <title>, meta description vs. payment form and visible text content)
credential harvesting
The page contains a prominent payment form collecting Email address, Name, Bank Name, and Amount via HTTP GET method ('method="get"'). Submitting via GET exposes all sensitive financial data (bank name, email, amount) directly in the URL query string, logging it in server logs, browser history, and referrer headers. This form is embedded in a non-banking site masquerading as an adtech SSP, strongly indicating credential and financial data harvesting. (location: page.html line 7: <form id='send-payment-form' method='get' ...> fields: Send-Pay-Email, Send-Pay-Name, Send-Bank-Name, Send-Pay-Amount)
phishing
The site presents itself as an AI-driven SSP (adtech/publisher platform) in its metadata and title, while the actual homepage prominently features payment collection forms requesting bank name, email, and financial amounts from users. This mismatch between stated purpose and actual content is a hallmark phishing technique — luring users under a professional tech veneer to extract financial information. (location: page.html: meta description ('AI-powered SSP') vs. pay-wrapper form section; page-text.txt line 7)
social engineering
The page uses fabricated social proof metrics with animated counter widgets ('People Use', 'Year Active', 'Happy Review', 'Happy Clients') but all counter digits are rendered as static 0-9 scrolling animations with no real values displayed. This manufactured credibility is used to pressure users into trusting the payment forms. Combined with phrases like 'Secure, fast, and hassle-free' and 'Effortless Payments, Tailored for You', this constitutes social engineering to build false trust. (location: page-text.txt lines 10, 28; page.html counter-section)
hidden content
The HTML contains a 'pay-blur-block' div wrapping the payment form with a close icon ('pay-close-icon'), suggesting the payment overlay is hidden by default (CSS display:none or opacity:0) and triggered programmatically. The form is present in the DOM but not immediately visible to casual inspection, concealing the credential-harvesting form from surface-level review. The class 'none' is also applied to the counter-section, indicating deliberate content visibility manipulation. (location: page.html: <div class='pay-blur-block'>, <section data-w-id='5194ce19...' class='counter-section none'>)
brand impersonation
The Webflow site ID and page ID (685aa3d798b08bdfcaf654f4) indicate this is a cloned or templated Webflow site. The service cards all display identical text 'Born in Gaming — We know what resonates because we built the platform that gamers trust' across multiple service categories (Financial Services, Shopping & Lifestyle, Recharge & Bill Payments), indicating a hastily assembled fake site using a copied template where placeholder content was never replaced, further evidencing impersonation of a legitimate business. (location: page.html lines 13-21: multiple .w-dyn-item service cards with identical content)
curl https://api.brin.sh/domain/omni-dex.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
omni-dex.io currently scores 32/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.