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 't-bank-app.ru' impersonates T-Bank (Tinkoff Bank), a major Russian financial institution. The '-app' suffix and '.ru' TLD are classic typosquatting/brand-abuse patterns used to deceive users into believing they are accessing an official banking app or service. (location: domain: t-bank-app.ru)
phishing
The domain 't-bank-app.ru' is highly consistent with a phishing site targeting T-Bank (Tinkoff) customers. The combination of brand name, 'app' keyword, and TLS failure (connected=false, cert_valid=false) indicates a site that either failed to load or is not serving a legitimate HTTPS service, a common characteristic of short-lived phishing infrastructure. (location: domain: t-bank-app.ru, metadata.json tls block)
credential harvesting
Banking brand impersonation domains of this pattern (bank-name + 'app' + country TLD) are predominantly used for credential harvesting — presenting fake login forms to steal usernames, passwords, and OTPs from banking customers. (location: domain: t-bank-app.ru)
malicious redirect
TLS connection failed entirely (connected=false), which may indicate the domain is parked, rotating infrastructure, or using HTTP redirects to deliver a payload or redirect victims to another phishing stage. The page content being empty is consistent with cloaking or bot-detection evasion that serves malicious content only to targeted victims. (location: metadata.json tls.connected=false, page.html (empty))
hidden content
All page content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the domain being resolvable enough to have metadata collected. This is consistent with cloaking techniques that serve empty or benign content to scanners while delivering malicious content to real users or specific geolocations. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/t-bank-app.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
t-bank-app.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.