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-16.co.uk' mimics AWS (Amazon Web Services) DNS infrastructure by incorporating 'awsdns' — a well-known AWS DNS hostname prefix — combined with a numeric suffix and a UK ccTLD. This pattern is designed to deceive users and automated systems into believing they are interacting with legitimate Amazon/AWS infrastructure. (location: domain: awsdns-16.co.uk)
phishing
The domain combines AWS brand impersonation with a .co.uk TLD, a classic typosquatting/lookalike domain technique used in phishing campaigns targeting AWS customers or organizations using AWS services. The TLS certificate is invalid and the site did not successfully connect (tls.connected=false, cert_valid=false), which is consistent with a dormant or newly-deployed phishing infrastructure. (location: metadata.json: tls.connected=false, tls.cert_valid=false, url=https://awsdns-16.co.uk)
social engineering
The awsdns-16.co.uk domain is structured to appear as a legitimate AWS DNS resolver or service endpoint (AWS Route 53 resolvers use hostnames like 'awsdns-XX.com/net/org/co.uk'). Targeting users or agentic systems that trust AWS DNS naming conventions, this could be used to redirect DNS queries, harvest credentials, or manipulate agent tool calls that resolve or trust this domain. (location: domain: awsdns-16.co.uk)
prompt injection
A domain spoofing AWS DNS infrastructure (awsdns-16.co.uk) could be weaponized in agentic pipelines: if an AI agent resolves or fetches content from this domain believing it to be a trusted AWS resource, any content served could contain prompt injection payloads. The empty page content at scan time may indicate the payload is served conditionally (e.g., only to specific user-agents or under specific conditions). (location: domain: awsdns-16.co.uk; page.html and page-text.txt are empty)
curl https://api.brin.sh/domain/awsdns-16.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-16.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.