context safety score
A score of 40/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-53.co.uk' directly impersonates AWS (Amazon Web Services) DNS infrastructure. AWS Route 53 DNS servers use the pattern 'awsdns' in their legitimate hostnames (e.g., ns-123.awsdns-45.com). This domain mimics that naming convention under a .co.uk TLD to deceive users and automated systems into believing they are interacting with official Amazon/AWS infrastructure. (location: domain: awsdns-53.co.uk)
phishing
The domain combines AWS brand identity ('awsdns') with a non-AWS TLD (.co.uk) — a classic phishing pattern designed to trick users or agents into trusting the domain as legitimate Amazon Web Services infrastructure. TLS connection failed (connected=false, cert_valid=false), meaning the site cannot establish a valid HTTPS connection, which is consistent with a malicious or abandoned phishing domain. (location: metadata.json: tls.connected=false, tls.cert_valid=false, domain=awsdns-53.co.uk)
credential harvesting
A domain impersonating AWS DNS infrastructure with no valid TLS certificate is a strong indicator of a credential harvesting setup targeting AWS account holders or systems that resolve DNS via Route 53. The AWS brand is frequently used in credential phishing campaigns targeting cloud credentials, IAM keys, and access tokens. (location: domain: awsdns-53.co.uk, metadata.json)
curl https://api.brin.sh/domain/awsdns-53.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-53.co.uk currently scores 40/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.