context safety score
A score of 44/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-57.co.uk' mimics AWS (Amazon Web Services) Route 53 DNS naming convention (awsdns-XX) but is registered under the .co.uk TLD rather than amazonaws.com. This is a common typosquatting/brand impersonation pattern targeting users and automated systems that associate 'awsdns' with legitimate Amazon infrastructure. (location: domain: awsdns-57.co.uk)
phishing
The domain impersonates AWS DNS infrastructure (awsdns-57.co.uk vs legitimate awsdns-57.amazon.com or amazonaws.com subdomains). Users or agents resolving or visiting this domain may be deceived into believing it is an official Amazon/AWS resource, enabling credential harvesting or malware delivery. (location: domain: awsdns-57.co.uk)
credential harvesting
TLS is not connected and certificate is invalid (connected=false, cert_valid=false). A site impersonating AWS infrastructure with no valid TLS is consistent with a credential harvesting setup that intercepts traffic or presents fake login forms without HTTPS protection. (location: metadata.json: tls block)
malicious redirect
The page returned empty HTML and text content despite the domain being reachable enough to generate metadata. This is consistent with a cloaked or redirect-based attack where content is conditionally served — e.g., only to specific user agents, geolocations, or referrers — hiding malicious redirects from scanners while serving them to real victims. (location: page.html, page-text.txt (empty content))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty, yet the domain is active with metadata collected. This absence of visible content is a strong indicator of cloaking — a technique used to hide malicious content from crawlers and security scanners while delivering it to targeted users. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/awsdns-57.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-57.co.uk currently scores 44/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.