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-19.net' closely mimics Amazon Web Services' legitimate DNS service branding (Route 53 uses 'awsdns' in its nameserver hostnames, e.g. ns-123.awsdns-45.com). The '.net' TLD combined with the 'awsdns-19' label is designed to deceive users and automated agents into believing this is an official AWS DNS endpoint. (location: domain: awsdns-19.net)
phishing
The domain impersonates AWS infrastructure naming conventions (awsdns-##) which are widely recognized as Amazon Route 53 nameservers. Registering a lookalike domain on a non-AWS TLD (.net) is a common phishing tactic to harvest credentials or redirect traffic from users expecting legitimate AWS services. (location: domain: awsdns-19.net)
hidden content
TLS connection failed (connected=false, cert_valid=false), meaning the site could not be crawled over HTTPS. The page HTML and visible text are completely empty, suggesting the site may only serve content under specific conditions (targeted delivery, IP filtering, or user-agent gating) to evade automated scanning while delivering malicious payloads to real targets. (location: metadata.json: tls.connected=false; page.html and page-text.txt are empty)
malicious redirect
The combination of an empty page response, failed TLS, and a brand-impersonating domain is consistent with a parked or conditionally-redirecting domain that serves benign or empty content to crawlers while redirecting human visitors or specific user-agents to a malicious destination. (location: domain: awsdns-19.net; page.html: empty)
curl https://api.brin.sh/domain/awsdns-19.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-19.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.