context safety score
A score of 48/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-52.net' impersonates AWS (Amazon Web Services) DNS infrastructure by mimicking the legitimate 'awsdns' naming pattern used by Route 53 nameservers (e.g., awsdns-01.com, awsdns-52.org). The '.net' TLD combined with numeric suffix is designed to appear as an official AWS DNS endpoint, deceiving users and automated systems. (location: domain: awsdns-52.net)
phishing
The domain closely mimics AWS Route 53 nameserver naming conventions. Users or agents resolving or visiting this domain may believe they are interacting with legitimate AWS infrastructure, enabling credential harvesting or traffic interception. (location: domain: awsdns-52.net)
credential harvesting
TLS is not connected and certificate is invalid (connected=false, cert_valid=false). A site impersonating AWS DNS without valid TLS is consistent with a credential harvesting setup where victims are lured under the assumption of a trusted AWS endpoint but their traffic or credentials are exposed. (location: metadata.json: tls block)
malicious redirect
The site returned empty page content (page.html and page-text.txt are empty) despite the domain being active. This is consistent with a parked or redirect-only domain that silently forwards victims to a malicious destination without rendering content that would be visible to scanners. (location: page.html, page-text.txt (empty content))
curl https://api.brin.sh/domain/awsdns-52.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-52.net currently scores 48/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.