context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'cbrpay.ru' mimics the Central Bank of Russia (CBR - Центральный Банк России), a major financial authority. The 'pay' suffix combined with the official abbreviation 'cbr' strongly suggests impersonation of the Central Bank of Russia's payment infrastructure to deceive users or financial systems. (location: domain: cbrpay.ru)
phishing
The site is hosted on a .ru TLD domain combining 'cbr' (Central Bank of Russia abbreviation) with 'pay', a classic phishing pattern targeting users expecting legitimate central bank payment portals. TLS connection failed (connected=false, cert_valid=false), meaning the site either does not serve HTTPS or presents an invalid certificate — a significant red flag for a site impersonating a financial institution. (location: domain: cbrpay.ru, TLS metadata)
credential harvesting
A domain impersonating a central bank payment service ('cbrpay.ru') with no valid TLS certificate is a high-risk credential harvesting vector. Users tricked into visiting this site expecting a legitimate banking payment portal may submit credentials or financial data over an insecure or spoofed connection. (location: domain: cbrpay.ru, TLS: connected=false, cert_valid=false)
social engineering
The domain construction 'cbrpay.ru' exploits the trusted acronym of Russia's Central Bank (CBR) combined with a payment-related keyword to socially engineer trust. This pattern is designed to lower user suspicion and induce interaction with a fraudulent financial service. (location: domain: cbrpay.ru)
curl https://api.brin.sh/domain/cbrpay.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
cbrpay.ru 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.