context safety score
A score of 36/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-01.co.uk' impersonates AWS (Amazon Web Services) DNS infrastructure. AWS uses 'awsdns' in its legitimate Route 53 nameserver hostnames (e.g., ns-xxx.awsdns-xx.com/net/org/co.uk), but those are subdomains of amazon-controlled TLDs. This domain registers 'awsdns-01.co.uk' as the apex domain itself, mimicking AWS branding to deceive users or automated systems into trusting it as legitimate AWS infrastructure. (location: domain: awsdns-01.co.uk)
phishing
The domain closely mimics AWS DNS naming conventions to likely intercept traffic, harvest credentials, or redirect users/agents who mistake it for legitimate AWS infrastructure. TLS is not connected and certificate is invalid, indicating the site is either down, blocking connections, or operating in a way that avoids SSL inspection. (location: domain: awsdns-01.co.uk, TLS status: connected=false, cert_valid=false)
malicious redirect
The domain appears to serve no visible content (empty page.html and page-text.txt) while using an AWS DNS impersonation name. This pattern is consistent with a domain used as a redirect intermediary, DNS hijacking endpoint, or C2 callback domain that only responds to specific requests or user-agents, evading automated crawlers. (location: domain: awsdns-01.co.uk, page.html: empty, page-text.txt: empty)
hidden content
The page HTML and visible text are completely empty despite the domain being reachable enough to have metadata collected. This blank-page pattern can indicate cloaking — serving different content to human browsers versus crawlers/scanners — which is a technique used to hide malicious payloads from automated security tools. (location: page.html: 0 bytes, page-text.txt: 0 bytes, page-hidden.txt: 0 bytes)
curl https://api.brin.sh/domain/awsdns-01.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-01.co.uk currently scores 36/100 with a suspicious verdict and low 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.