context safety score
A score of 48/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 'monetate-prod.zone' impersonates Monetate, a legitimate e-commerce personalization platform (monetate.com). The use of a non-standard TLD '.zone' combined with a production-sounding subdomain pattern ('monetate-prod') is a classic brand impersonation technique designed to deceive users and automated systems into trusting the domain as an official Monetate infrastructure endpoint. (location: domain: monetate-prod.zone)
malicious redirect
TLS connection failed (connected=false, cert_valid=false) for a domain impersonating a legitimate SaaS brand. The site cannot be reached over HTTPS despite using an HTTPS URL, which may indicate the domain is parked, used for DNS-based redirection, or configured to intercept traffic at a lower layer. This pattern is consistent with a domain used as a redirect or traffic interception node. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
phishing
The domain 'monetate-prod.zone' combines a well-known SaaS brand name with a production-environment label under a low-credibility TLD ('.zone'). This combination is characteristic of phishing infrastructure targeting developers, DevOps engineers, or automated agents that interact with Monetate APIs, potentially to harvest API keys, OAuth tokens, or session credentials by posing as a legitimate Monetate production endpoint. (location: domain: monetate-prod.zone)
credential harvesting
A domain impersonating a SaaS production environment (Monetate) with no valid TLS certificate is a strong indicator of a credential harvesting setup. Automated agents or CI/CD pipelines configured to communicate with 'monetate-prod.zone' endpoints could be tricked into submitting API credentials or authentication tokens to an attacker-controlled server. (location: metadata.json: domain=monetate-prod.zone, tls.cert_valid=false)
curl https://api.brin.sh/domain/monetate-prod.zoneCommon questions teams ask before deciding whether to use this domain in agent workflows.
monetate-prod.zone currently scores 48/100 with a suspicious verdict and medium 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.