context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain forexpros.com serves content that fully impersonates investing.com (Fusion Media / Investing.com brand). The page renders the complete Investing.com site including its logo, navigation, footer copyright, and canonical tag pointing to https://www.investing.com. The visited domain (forexpros.com) has no disclosed relationship to investing.com, presenting a classic domain-squatting brand impersonation scenario. (location: page.html: <link rel="canonical" href="https://www.investing.com"> and full page branding; metadata.json: domain=forexpros.com)
malicious redirect
The canonical URL and all internal links point to www.investing.com, not forexpros.com. The page is structured to funnel users from the typosquat/lookalike domain forexpros.com into the investing.com ecosystem, or alternatively to intercept traffic intended for investing.com before redirecting or serving a cloned version. All hrefLang alternate links and logo href also resolve to investing.com domains. (location: page.html: canonical and alternate link tags in <head>; logo href https://www.investing.com/)
social engineering
The site presents prominent 'Sign In' and 'Free Sign Up' calls-to-action consistent with credential harvesting setup under a brand-impersonation scenario. Users landing on forexpros.com believing it to be a legitimate financial data site may be induced to register or log in, submitting credentials to an unverified domain. (location: page-text.txt: 'Sign In Free Sign Up' UI elements; page.html: header sign-in/sign-up buttons)
curl https://api.brin.sh/domain/forexpros.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
forexpros.com currently scores 33/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.