context safety score
A score of 32/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-08.co.uk' mimics AWS (Amazon Web Services) DNS infrastructure by incorporating 'awsdns' — a well-known AWS Route 53 nameserver prefix — into a .co.uk TLD. This is a classic typosquatting/brand impersonation pattern designed to deceive users or automated systems into trusting the domain as legitimate Amazon infrastructure. (location: domain: awsdns-08.co.uk)
phishing
The domain impersonates AWS DNS services (awsdns-08.co.uk) while using a .co.uk TLD rather than the legitimate .com used by Amazon. This mismatch is a hallmark phishing technique to lure victims who may misread or trust the 'awsdns' prefix as authentic Amazon infrastructure. (location: domain: awsdns-08.co.uk)
credential harvesting
A domain impersonating AWS DNS infrastructure is a high-risk vector for credential harvesting. Actors registering AWS-lookalike domains commonly deploy fake AWS console login pages to capture IAM credentials, AWS account passwords, or MFA tokens from victims who trust the domain name. (location: domain: awsdns-08.co.uk)
social engineering
The domain name 'awsdns-08.co.uk' is engineered to exploit implicit trust in AWS infrastructure naming conventions (e.g., ns-1.awsdns-08.co.uk mirrors real AWS nameserver patterns). This social engineering via domain naming targets both human users and automated systems/agents that may accept the domain as a legitimate AWS resource. (location: domain: awsdns-08.co.uk)
prompt injection
A domain crafted to look like AWS DNS infrastructure could be used to serve malicious content to AI agents or automated crawlers that resolve or interact with AWS-related endpoints. If an AI agent is configured to trust awsdns-prefixed domains as authoritative AWS sources, adversarial instructions could be injected via this domain's responses. (location: domain: awsdns-08.co.uk)
malicious redirect
TLS is not connected and the certificate is invalid (connected=false, cert_valid=false) for a domain impersonating AWS infrastructure. This indicates the site may be intercepting or redirecting traffic without a valid secure channel, consistent with a man-in-the-middle or malicious redirect setup targeting users expecting secure AWS service endpoints. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/awsdns-08.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-08.co.uk currently scores 32/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.