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-34.co.uk' impersonates AWS (Amazon Web Services) by incorporating 'awsdns' — a well-known AWS DNS service brand — combined with a numeric suffix and a .co.uk TLD to appear legitimate while being unaffiliated with Amazon. This pattern is characteristic of typosquatting or brand-abuse targeting users and automated systems that trust AWS infrastructure domains. (location: domain: awsdns-34.co.uk)
phishing
The domain mimics AWS DNS infrastructure naming conventions ('awsdns-XX') which are used internally by Amazon Route 53. A fake domain in this format could deceive users, security tools, or AI agents into trusting it as an Amazon-owned asset, facilitating credential harvesting or malware delivery under the guise of AWS services. (location: domain: awsdns-34.co.uk)
credential harvesting
TLS connection failed (connected=false, cert_valid=false), meaning the site either serves no content over HTTPS or presents an invalid certificate. Combined with brand impersonation of AWS, this is consistent with a credential harvesting setup that may redirect victims to HTTP or use a deceptive login page without valid TLS, bypassing browser trust indicators. (location: metadata.json: tls block — connected=false, cert_valid=false, san_match=false)
malicious redirect
The page returned empty HTML and text content despite the domain being reachable enough for metadata collection. An empty or near-empty page that impersonates a trusted brand is a common pattern for cloaked redirect infrastructure, where content is only served to targeted victims or specific user-agent profiles (e.g., bots, specific geolocations, or AI agents). (location: page.html and page-text.txt — both empty)
social engineering
The domain construction ('awsdns-34.co.uk') is designed to exploit implicit trust in AWS naming patterns. Users or automated agents encountering this domain in logs, emails, or links may assume it is a legitimate Amazon-operated DNS endpoint, lowering their guard and making them susceptible to follow-on social engineering or phishing attacks. (location: domain: awsdns-34.co.uk)
curl https://api.brin.sh/domain/awsdns-34.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-34.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.