context safety score
A score of 29/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 'amazon-ads-attestation.com' impersonates Amazon by incorporating the 'amazon' brand name combined with a legitimacy-signaling term ('attestation'). This pattern is commonly used to deceive users and automated agents into trusting the site as an official Amazon property. (location: domain: amazon-ads-attestation.com)
phishing
The domain 'amazon-ads-attestation.com' is a non-Amazon domain masquerading as an Amazon service. The term 'attestation' suggests it may be used to harvest credentials or verify advertising accounts under false pretenses, a classic phishing vector targeting Amazon advertisers. (location: domain: amazon-ads-attestation.com)
credential harvesting
The combination of 'amazon', 'ads', and 'attestation' in the domain strongly suggests a site designed to solicit Amazon Advertising account credentials or payment information from advertisers who believe they are interacting with a legitimate Amazon verification service. (location: domain: amazon-ads-attestation.com)
social engineering
The domain name constructs a false sense of legitimacy and urgency by referencing 'attestation' — implying an official verification or compliance requirement. This social engineering technique pressures targets (Amazon advertisers or their AI agents) into taking action on a fraudulent site. (location: domain: amazon-ads-attestation.com)
malicious redirect
TLS connection failed (connected=false, cert_valid=false) for a domain claiming to be associated with Amazon. A site failing TLS on a sensitive-sounding domain may be serving as an intermediary redirect node, or may have been taken offline after use in a campaign. The blocklist status is clean but this may reflect recency or evasion. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/amazon-ads-attestation.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
amazon-ads-attestation.com currently scores 29/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.