context safety score
A score of 36/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 'amzndns-cn.net' closely mimics Amazon ('amzn') combined with a DNS-service pattern and a Chinese-market TLD suffix ('cn'), a classic typosquatting/brand-impersonation technique designed to deceive users or automated agents into trusting an Amazon-affiliated service. (location: domain: amzndns-cn.net)
phishing
The domain impersonates Amazon infrastructure ('amzndns-cn.net') with no valid TLS certificate (TLS connected=false, cert_valid=false), which is characteristic of a phishing site that has not yet fully deployed or is being used for credential harvesting under a deceptive brand. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Combination of Amazon brand impersonation via domain name, invalid TLS, and unknown hosting reputation creates a high-risk profile consistent with credential harvesting infrastructure targeting Amazon account holders. (location: domain: amzndns-cn.net; metadata.json: hosting.reputation=Unknown)
malicious redirect
Domain pattern 'amzndns-cn.net' may function as a DNS or redirect intermediary, routing victims through a deceptive Amazon-lookalike domain before forwarding to a malicious payload or data-collection endpoint. No page content was returned, consistent with a redirect-only or not-yet-activated infrastructure node. (location: domain: amzndns-cn.net; page.html: empty)
curl https://api.brin.sh/domain/amzndns-cn.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
amzndns-cn.net currently scores 36/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.