context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed (connected=false, cert_valid=false, san_match=false) for gosuslugi.ru — the official Russian e-government portal. Inability to establish a valid TLS session means traffic could be intercepted or the page served is not from the legitimate origin, indicating a possible man-in-the-middle scenario or spoofed endpoint. (location: metadata.json: tls block)
brand impersonation
gosuslugi.ru is the official Russian Federation public services portal (Gosuslugi). A failed TLS handshake combined with empty page content strongly suggests this may be a spoofed or intercepted version of the site. Legitimate high-value government portals do not fail TLS validation, making this a strong indicator of brand impersonation infrastructure. (location: metadata.json: domain=gosuslugi.ru, tls.connected=false)
credential harvesting
gosuslugi.ru handles Russian citizen authentication, passport data, tax, pension, and other sensitive government credentials. A TLS-invalid, content-empty rendition of this site is consistent with a credential-harvesting proxy or clone that captures login submissions before forwarding them. (location: metadata.json + page.html (empty content despite live domain))
phishing
The combination of a high-value government brand (gosuslugi.ru), failed TLS certificate validation, and completely empty harvested page content is a classic phishing infrastructure pattern: a domain or proxy that mimics a trusted site but cannot reproduce its legitimate TLS certificate, and whose content was either blocked or stripped during capture. (location: metadata.json: tls.cert_valid=false, tls.san_match=false; page.html: empty)
curl https://api.brin.sh/domain/gosuslugi.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
gosuslugi.ru currently scores 43/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.