context safety score
A score of 35/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 'phoenix-browser-update.ru' impersonates a legitimate browser update service using a well-known browser name ('Phoenix') combined with 'browser-update' to deceive users into believing the site is an official browser update distribution channel. (location: domain: phoenix-browser-update.ru)
social engineering
The domain pattern '[product]-browser-update.[tld]' is a classic social engineering lure used to trick users into downloading malware disguised as a browser update. The .ru TLD combined with this naming convention is a well-documented malware distribution pattern. (location: domain: phoenix-browser-update.ru)
malicious redirect
TLS connection failed (connected=false, cert_valid=false), yet the domain is structured as a browser update site. Sites that fail TLS validation but use update-themed domains commonly serve as intermediary redirectors to malware payloads or further phishing stages. The page content is empty, consistent with a cloaked/redirecting landing page that only activates for real browser visits. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
phishing
The URL 'https://phoenix-browser-update.ru' uses HTTPS in the URL while TLS is not actually connected and cert is invalid. The combination of a fake browser update domain, failed TLS, empty page content (evasion of automated scanners), and .ru registrar is a high-confidence phishing/malware delivery pattern targeting end users seeking browser updates. (location: domain: phoenix-browser-update.ru; metadata.json tls block)
hidden content
Page HTML and visible text are completely empty, yet the domain is live and registered. Empty content returned to automated scanners is a known cloaking technique: real content (malicious downloads, credential forms) is served only to human visitors or specific user-agents, evading automated threat detection. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/phoenix-browser-update.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
phoenix-browser-update.ru currently scores 35/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.