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
The domain 'awstrack.me' uses 'aws' as a prefix, strongly implying affiliation with Amazon Web Services (AWS). The use of a '.me' TLD instead of an official Amazon domain (e.g., amazonaws.com, aws.amazon.com) is a well-known brand impersonation tactic used to deceive users and automated agents into trusting the domain as legitimate AWS infrastructure. (location: domain: awstrack.me)
malicious redirect
The domain 'awstrack.me' follows the pattern of tracking/redirect services that impersonate AWS. Such domains are commonly used as intermediary redirect hops in phishing campaigns, click-tracking abuse, or email link wrapping to obscure the final malicious destination. TLS connection failed entirely (connected=false, cert_valid=false), suggesting the domain may be dormant, parked, or serving as a passive redirect placeholder. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
phishing
The combination of AWS brand impersonation in the domain name, failed TLS, WHOIS privacy redaction, and unknown hosting reputation are consistent with a phishing infrastructure domain. The site returned no content (empty HTML and text), which is typical of parked phishing domains awaiting activation or used solely as redirect intermediaries in phishing email chains. (location: domain: awstrack.me; metadata.json: tls, whois, hosting fields)
hidden content
The page rendered no visible text or HTML content despite the domain being live enough to be scanned. Empty page content with a registered domain and WHOIS privacy redaction may indicate cloaking — serving content only to targeted victims or specific user-agents/IPs while appearing blank to scanners. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/awstrack.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
awstrack.me 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.