context safety score
A score of 40/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 loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
prompt injection
Hidden HTML element contains AI-targeting instructions
brand impersonation
The domain okx.ac impersonates the legitimate OKX cryptocurrency exchange (okx.com). The site clones OKX branding, logos, content, and UI in full, operating under a deceptive alternative TLD (.ac instead of .com). The canonical copyright tag reads 'okx.com' while the actual serving domain is okx.ac. The og:url and schema.org Organization URL both reference 'https://www.okx.ac', confirming intentional branding substitution on a non-official domain. (location: metadata.json:domain, page.html:1 (meta name=Copyright content=okx.com, og:url=https://www.okx.ac/en-us))
phishing
The site is a full replica of the OKX crypto exchange hosted on okx.ac — a domain distinct from the legitimate okx.com. It presents authentic-looking login, registration, and trading interfaces to deceive users into submitting credentials and financial information. The site prompts users to 'Register now' and interact with trading/wallet features, all funneled through an unauthorized domain. (location: page-text.txt:1 (Register now CTA), page.html:1 (title: Buy Bitcoin & Crypto | OKX United States))
credential harvesting
The site replicates the full OKX exchange interface including login, registration, and account management flows on a non-official domain (okx.ac). Users who enter credentials believe they are logging into legitimate OKX accounts. The infrastructure is designed to capture usernames, passwords, and potentially 2FA tokens from crypto exchange users. (location: page.html:1 (full exchange UI with nav: Sign up, Log in implied by exchange clone structure), page-text.txt:1)
malicious redirect
The schema.org structured data and og:url tags reference 'https://www.okx.ac' as the canonical organization URL, while all static assets (CSS, JS, images) are loaded from 'static.okx.com' — the legitimate OKX CDN. This cross-domain asset loading pattern is consistent with a mirrored phishing site that proxies or clones the real site, potentially intercepting user sessions and redirecting authentication flows to attacker-controlled infrastructure. (location: page.html:2-3 (link rel=stylesheet href=https://static.okx.com/...), page.html:5 (script src=https://static.okx.com/...))
brand impersonation
The site's structured data (application/ld+json) declares the Organization name as 'OKX United States' with url 'https://www.okx.ac', and lists alternateName entries including 'OKX.com' and 'Okex', directly associating the fraudulent domain with the legitimate brand identity. The legalName 'Aux Cayes FinTech Co. Ltd.' matches OKX's real legal entity, further deepening the impersonation. (location: page.html:line with application/ld+json Organization schema, page-text.txt:81)
curl https://api.brin.sh/domain/okx.acCommon questions teams ask before deciding whether to use this domain in agent workflows.
okx.ac currently scores 40/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.