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
The domain 'awsdns-33.net' mimics Amazon Web Services (AWS) DNS infrastructure by incorporating 'awsdns' — a well-known AWS Route 53 nameserver hostname pattern — combined with a numeric suffix and a non-AWS TLD (.net instead of .amazonaws.com). This is a classic typosquat/lookalike domain designed to impersonate AWS infrastructure services and deceive users or automated systems into trusting the domain. (location: domain: awsdns-33.net)
phishing
The domain closely imitates Amazon Route 53 nameserver naming conventions (e.g., ns-xxx.awsdns-xx.net) to lure victims who may believe they are interacting with legitimate AWS DNS infrastructure. The TLS connection failed (connected=false, cert_valid=false), which is consistent with a staged or inactive phishing domain that has not yet deployed a certificate, or is blocking automated scanning. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The site returned no page content (page.html and page-text.txt are empty) despite being a registered domain with no blocklist entry. This blank response is consistent with a domain parked for future malicious use, cloaking content from scanners/bots, or serving redirects only to targeted user-agents/browsers — a common evasion technique in phishing and redirect campaigns. (location: page.html (empty), page-text.txt (empty))
hidden content
The page-hidden.txt file is empty, yet the domain is active and registered. Combined with the TLS failure and empty HTML, the absence of any detectable content suggests deliberate cloaking: content may only be served to specific user agents, IP ranges, or referrers — a technique used to hide malicious payloads from automated scanners while delivering them to real victims. (location: page-hidden.txt (empty), page.html (empty))
curl https://api.brin.sh/domain/awsdns-33.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-33.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.