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-48.net' closely mimics Amazon Web Services' legitimate DNS infrastructure domain 'awsdns.net' / Route 53 nameserver pattern (e.g., ns-*.awsdns.com). The '.net' TLD combined with the 'awsdns' prefix is a typosquat/lookalike pattern designed to impersonate AWS DNS services. (location: domain: awsdns-48.net)
phishing
The domain impersonates AWS DNS infrastructure (awsdns-48.net vs legitimate AWS nameservers like ns-*.awsdns.com/net/org/co.uk). This pattern is commonly used to deceive users or automated systems into trusting the domain as an official AWS resource, enabling credential harvesting or malware delivery. (location: domain: awsdns-48.net)
hidden content
TLS connection failed (connected=false, cert_valid=false) meaning the page content could not be retrieved or verified. Empty page.html, page-text.txt, and page-hidden.txt suggest the site either blocks crawlers, serves content only under specific conditions (cloaking), or is in a pre-activation/parked state awaiting deployment — all consistent with evasion techniques used by malicious infrastructure. (location: metadata.json: tls.connected=false; page.html, page-text.txt, page-hidden.txt (all empty))
malicious redirect
A domain impersonating AWS DNS infrastructure with no accessible content and failed TLS is consistent with a parked or staged malicious domain that may be used for DNS hijacking, traffic interception, or redirect campaigns targeting users who mistype or are deceived into visiting an AWS-lookalike URL. (location: domain: awsdns-48.net; metadata.json: tls.connected=false)
curl https://api.brin.sh/domain/awsdns-48.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-48.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.