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
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
brand impersonation
The domain okta-emea.com is not an official Okta domain. The page serves a full clone of the legitimate Okta homepage (www.okta.com), including Okta branding, logos, product listings, and navigation, from a lookalike domain designed to impersonate the Okta brand. The canonical URL in the HTML is set to https://www.okta.com/ (line 20), confirming the content is mirrored from the real site. (location: domain: okta-emea.com; page.html line 20: <link rel="canonical" href="https://www.okta.com/"/>)
phishing
The site presents a pixel-perfect replica of the official Okta identity platform homepage on a lookalike domain (okta-emea.com vs okta.com). It includes a prominent Login link pointing to https://login.okta.com/, which could be swapped or used to harvest credentials from users who believe they are on the legitimate Okta site. The EMEA-themed subdomain name is designed to deceive Okta customers in Europe into trusting the site. (location: page.html line 381-384: Login link; domain okta-emea.com)
credential harvesting
The page clones Okta's login flow entry point. The Login CTA links to https://login.okta.com/ and the page contains JavaScript that hashes emails (hashEmail function using SHA-256) and reads/writes attribution cookies (_okta_attribution, _okta_session_attribution, _okta_original_attribution). On a fraudulent lookalike domain, this infrastructure could be trivially modified to intercept credentials or track users before redirecting them to the real login. (location: page.html lines 174-181: hashEmail function; lines 128-173: attribution cookie tracking)
malicious redirect
The page is hosted at okta-emea.com but all internal navigation links and CTAs point to www.okta.com, okta.com, login.okta.com, auth0.com, and other legitimate Okta-owned domains. This pattern is consistent with a transparent reverse-proxy or content-mirroring attack where the attacker intercepts traffic before passing it to the real site, enabling session hijacking or credential interception in transit. (location: page.html: multiple href targets including https://login.okta.com/ (line 381), https://www.okta.com/ throughout)
social engineering
The lookalike domain okta-emea.com uses a plausible EMEA (Europe, Middle East, Africa) regional subdomain pattern to appear as a legitimate Okta regional portal. This exploits user trust in regional subdomains for large enterprise software vendors and is a known social engineering technique to target enterprise employees in the EMEA region who may expect a region-specific URL. (location: domain: okta-emea.com; .brin-context.md line 4)
curl https://api.brin.sh/domain/okta-emea.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
okta-emea.com 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.