context safety score
A score of 32/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 'zscaler9.net' impersonates Zscaler, a well-known cybersecurity company (zscaler.com). The appended digit '9' is a classic typosquatting/brand impersonation technique used to deceive users and AI agents into trusting the domain as legitimate Zscaler infrastructure. (location: domain: zscaler9.net)
phishing
The domain zscaler9.net mimics the legitimate Zscaler security brand. Such impersonation domains are commonly used for phishing attacks targeting enterprise users who trust Zscaler as a security vendor, potentially harvesting credentials or delivering malicious payloads under the guise of a trusted security tool. (location: domain: zscaler9.net)
credential harvesting
A domain impersonating a cybersecurity vendor (Zscaler) with no valid TLS certificate (TLS connected=false, cert_valid=false) is a strong indicator of a credential harvesting site. Users or agents directed here may be prompted to enter enterprise credentials believing they are interacting with legitimate Zscaler services. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
malicious redirect
The site returned empty page content (page.html and page-text.txt are empty) despite the domain being accessible for scanning. This is consistent with cloaking behavior — serving different content to scanners vs. real users/agents, or redirecting visitors to a malicious destination not captured in the static fetch. (location: page.html (empty), page-text.txt (empty))
hidden content
The page-hidden.txt file is empty and page.html contains no content, yet the domain resolves and was reachable enough to scan. The absence of visible or hidden content alongside a brand-impersonating domain suggests possible cloaking, bot-detection-based content suppression, or dynamic content delivery designed to evade automated analysis. (location: page-hidden.txt (empty), page.html (empty))
curl https://api.brin.sh/domain/zscaler9.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
zscaler9.net currently scores 32/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.