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
Domain 'awsdns-03.co.uk' mimics AWS (Amazon Web Services) DNS infrastructure by incorporating 'awsdns' — a well-known AWS Route 53 nameserver prefix — combined with a numeric suffix and a non-AWS TLD (.co.uk). This pattern is characteristic of typosquatting or brand impersonation targeting AWS customers and automated systems that may trust AWS-branded domains. (location: domain: awsdns-03.co.uk)
phishing
The domain closely imitates legitimate AWS DNS hostnames (e.g., ns-NNN.awsdns-NN.co.uk) used by Amazon Route 53. Victims or AI agents resolving or visiting this domain may be deceived into believing they are interacting with official AWS infrastructure, enabling credential harvesting or malicious payload delivery. (location: domain: awsdns-03.co.uk)
credential harvesting
TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no valid HTTPS or is not currently active. However, a domain impersonating AWS DNS infrastructure with broken/absent TLS is consistent with a credential harvesting setup targeting AWS IAM, console logins, or API key submissions, potentially under construction or selectively activated. (location: metadata.json: tls block)
malicious redirect
The page returned no content (page.html and page-text.txt are empty) despite the domain being reachable enough to scan. Empty content combined with brand impersonation of AWS DNS infrastructure suggests the domain may be used as a redirect intermediary or parking page that activates conditionally (e.g., based on user-agent, referrer, or geolocation). (location: page.html, page-text.txt (empty content))
curl https://api.brin.sh/domain/awsdns-03.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-03.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.