context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
Inline JavaScript immediately executes window.location.replace('https://app.elationemr.com/oidc/callback') on page load, forcibly redirecting all visitors away from the landing page before any content is rendered. This bypasses normal navigation and prevents back-button use, a common technique in phishing redirect chains. (location: page.html:8 - <script> in <head>)
brand impersonation
The page title reads 'Elation Health - Bad Request' and uses an Okta CDN-hosted logo (ok12static.oktacdn.com) with alt text 'Elation Health', combining Okta infrastructure with Elation Health branding. This conflation of two distinct brands on an error page is anomalous and consistent with a spoofed or misconfigured identity provider page designed to harvest credentials under a trusted brand facade. (location: page.html:6,23)
credential harvesting
The page exposes a live Okta OIDC client admin URL (https://dev-5847984-admin.okta.com/admin/app/oidc_client/instance/0oa3gd6l7B8kzsGLl5d6#tab-general) in both the visible error message and page body. This reveals a developer/staging Okta tenant ID and app instance ID, which could be used to probe or attack the OAuth application configuration. Exposure of internal admin panel URLs in user-facing error output is a sensitive information disclosure risk. (location: page.html:32,71 - error message body)
hidden content
A <style> block sets '#st-app { display: none; }' and an immediately following <span id='st-app'> contains the text 'END_USER_APP'. This hidden element is not part of the visible UI and its purpose is unexplained. Hidden sentinel strings injected into pages can be used for bot detection evasion, fingerprinting, or as prompt injection anchors targeting AI agents that process page text. (location: page.html:58-62)
prompt injection
The string 'END_USER_APP' is placed inside a CSS-hidden <span> element rendered outside the main widget container. AI agents or scrapers that extract page text (as seen in page-text.txt:45) will encounter this token injected into their text context. This is a pattern consistent with prompt injection targeting LLM-based agents, where hidden tokens attempt to manipulate agent behavior or classification. (location: page.html:62; page-text.txt:45)
social engineering
The page presents an official-looking 'Bad Request / 400' error with Okta and Elation Health branding, a 'Go to Homepage' button, and a 'Technical details' disclosure toggle. This mimics a legitimate authentication error page to build user trust before the JavaScript redirect fires, reducing suspicion while the redirect to the OIDC callback endpoint proceeds. (location: page.html:18-42)
curl https://api.brin.sh/domain/elationemr.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
elationemr.com currently scores 37/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.