context safety score
A score of 32/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 'awsdns-cn-03.biz' impersonates Amazon Web Services (AWS) DNS infrastructure by mimicking the legitimate 'awsdns' naming convention used by Route 53 (e.g., ns-*.awsdns.com). The use of a .biz TLD combined with a country-code infix 'cn' and numeric suffix is a classic typosquatting/brand-impersonation pattern designed to deceive users and automated systems into trusting it as an official AWS DNS endpoint. (location: domain: awsdns-cn-03.biz)
phishing
The domain closely mimics AWS Route 53 DNS nameserver naming (awsdns-XX.TLD) on a non-AWS TLD (.biz), consistent with infrastructure used in phishing campaigns targeting AWS customers or systems that perform DNS-based trust checks. TLS is not valid and the site did not connect successfully, which is consistent with a parked or early-stage phishing domain. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The domain is unreachable via HTTPS (TLS connected=false, cert_valid=false, san_match=false) yet is registered and active. This pattern is common for domains held in reserve for malicious redirect infrastructure, DNS hijacking, or man-in-the-middle interception of traffic expecting legitimate AWS DNS responses. (location: metadata.json: tls block)
social engineering
The domain name 'awsdns-cn-03.biz' is crafted to appear as a legitimate AWS DNS server, which could socially engineer users, developers, or automated agents into trusting DNS responses, certificates, or network traffic originating from this domain. The authoritative-sounding numeric suffix and regional infix ('cn') reinforce false legitimacy. (location: domain: awsdns-cn-03.biz)
curl https://api.brin.sh/domain/awsdns-cn-03.bizCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-cn-03.biz currently scores 32/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.