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-56.co.uk' closely mimics Amazon Web Services (AWS) DNS branding by incorporating 'awsdns' — a well-known AWS infrastructure subdomain pattern — combined with a numeric suffix and a .co.uk TLD. This is a classic typosquatting/brand impersonation technique designed to deceive users or automated systems into trusting a domain as legitimate AWS infrastructure. (location: domain: awsdns-56.co.uk)
phishing
The domain impersonates AWS DNS naming conventions (awsdns-XX.tld is the format AWS uses for its Route 53 nameservers) under a non-AWS TLD (.co.uk). This pattern is commonly used in phishing campaigns targeting AWS customers or systems that resolve/trust AWS-like hostnames. TLS is not connected and certificate is invalid, which is atypical for any legitimate infrastructure service. (location: domain: awsdns-56.co.uk, TLS: connected=false, cert_valid=false)
malicious redirect
The site returned no page content (empty HTML and text), which is consistent with a parked domain, a cloaked redirect, or a site that serves content only under specific conditions (e.g., to specific user agents, referrers, or geolocations). This evasion technique is used to avoid detection by scanners while still redirecting real victims. (location: page.html (empty), page-text.txt (empty))
hidden content
No visible or hidden content was rendered, yet the domain is active. The complete absence of content combined with brand impersonation of AWS DNS infrastructure suggests the site may conditionally serve malicious payloads or redirect pages only to targeted traffic, hiding its true behavior from automated analysis tools. (location: page.html (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/awsdns-56.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-56.co.uk 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.