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-18.co.uk' mimics Amazon Web Services (AWS) DNS infrastructure by incorporating 'awsdns' — a subdomain pattern used by AWS Route 53 name servers (e.g., ns-123.awsdns-18.com). Registering this as a standalone .co.uk domain impersonates AWS to deceive users or automated systems into trusting it as legitimate AWS infrastructure. (location: domain: awsdns-18.co.uk)
phishing
The domain closely imitates AWS Route 53 nameserver naming conventions (awsdns-##.tld) under a British ccTLD (.co.uk), a common technique to lure victims — particularly cloud engineers or automated DNS resolution systems — into believing they are interacting with genuine AWS DNS infrastructure. (location: domain: awsdns-18.co.uk)
malicious redirect
TLS connection failed (connected=false, cert_valid=false), yet the domain is registered and resolving. This is consistent with a domain used as an intermediary hop or redirect destination where TLS is not configured, possibly acting as a non-HTTPS redirect or tracking endpoint in a multi-stage attack chain. (location: metadata.json: tls block)
hidden content
The page returned empty HTML, empty visible text, and empty hidden content despite the domain being active. A live domain serving no content is a strong indicator of a dormant or cloaked threat — content may be served selectively based on user-agent, IP geolocation, referrer, or other fingerprinting signals to evade automated scanners. (location: page.html, page-text.txt, page-hidden.txt)
curl https://api.brin.sh/domain/awsdns-18.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-18.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.