context safety score
A score of 46/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 entirely (connected=false, cert_valid=false, san_match=false) for a domain presenting itself as an API service. Legitimate API platforms invariably have valid TLS. This pattern is consistent with a site that intercepts or redirects API traffic, rotates infrastructure, or is used as a staging/phishing endpoint where TLS is intentionally absent to avoid certificate transparency log scrutiny. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The domain name 'molniya-api.com' mimics the naming convention of legitimate API service providers (e.g., OpenAI API, Anthropic API, etc.) by appending '-api' to a distinctive word. 'Molniya' is a Russian word meaning 'lightning', which is also a brand name used in satellite and communication contexts. This construction is a known typosquatting and brand-impersonation pattern used to deceive AI agents or developers into sending API credentials to a fraudulent endpoint. (location: metadata.json: domain=molniya-api.com)
credential harvesting
A domain styled as an API service ('molniya-api.com') with no valid TLS and no page content is a strong indicator of a credential harvesting endpoint. Developers or AI agents configured to call this API would transmit API keys, bearer tokens, or other secrets over an insecure or adversarially-controlled connection. The absence of any legitimate page content reinforces that the site has no authentic service purpose. (location: metadata.json: domain=molniya-api.com, tls.connected=false)
prompt injection
An API-named domain with no content and failed TLS is consistent with infrastructure used in prompt injection attacks against AI agents: an agent could be instructed (via injected instructions in a document or tool response) to exfiltrate data by making a request to this endpoint. The '-api.com' naming makes it appear benign in agent reasoning traces. (location: metadata.json: domain=molniya-api.com)
curl https://api.brin.sh/domain/molniya-api.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
molniya-api.com currently scores 46/100 with a suspicious verdict and medium 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.