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-50.co.uk' mimics AWS (Amazon Web Services) DNS infrastructure naming conventions. The pattern 'awsdns-' is used by Amazon Route 53 resolvers (e.g., ns-*.awsdns-*.com), and this domain spoofs that pattern on a .co.uk TLD to appear legitimate. (location: domain: awsdns-50.co.uk)
phishing
The domain impersonates AWS DNS infrastructure under a .co.uk TLD with no valid TLS certificate (TLS connection failed, cert_valid=false). This combination — brand impersonation plus absent SSL — is a strong phishing indicator, commonly used to harvest AWS credentials or redirect users believing they are interacting with Amazon services. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
A domain spoofing AWS DNS naming (awsdns-50.co.uk) with failed TLS and empty page content is consistent with a credential harvesting setup — either serving login forms dynamically, acting as a backend collection endpoint, or being used in targeted spear-phishing emails directing victims to fake AWS console pages. (location: domain: awsdns-50.co.uk, metadata.json)
malicious redirect
The page returned no content (page.html and page-text.txt are empty) despite the domain being active enough to resolve. This blank-page pattern is consistent with a redirect intermediary or a parked malicious domain that serves payloads conditionally (e.g., only to specific user agents, referrers, or geolocations), evading static crawlers. (location: page.html (empty), page-text.txt (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are empty, yet the domain is registered and active. Content may be served conditionally to real victims while withholding it from scanners, a known evasion technique used by phishing kits and malware distribution sites. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/awsdns-50.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
awsdns-50.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.