context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain ivanticloud.com impersonates Ivanti, a well-known enterprise IT security and service management software vendor. The domain appends 'cloud' to the Ivanti brand, a common phishing tactic to create a convincing lookalike domain targeting Ivanti customers and users. (location: domain: ivanticloud.com)
brand impersonation
The domain ivanticloud.com directly incorporates the 'Ivanti' brand name (ivanti.com is the legitimate domain). Adding 'cloud' is a typosquatting/brandjacking technique used to deceive users into believing they are interacting with an official Ivanti cloud service. (location: domain: ivanticloud.com)
credential harvesting
A domain impersonating a major enterprise security vendor (Ivanti) with a failed TLS connection and empty page content is consistent with a credential harvesting setup — users arriving may be redirected or served login-spoofing pages dynamically. The TLS failure (connected=false, cert_valid=false) means any credentials submitted would also be transmitted insecurely. (location: domain: ivanticloud.com, tls: connected=false)
malicious redirect
The page returned empty HTML and text content despite the domain being reachable enough for metadata to be collected. This blank-page pattern is commonly used in redirect chains where the real malicious payload is delivered via JavaScript redirects or HTTP-level redirects not captured in static content. The domain may serve as a redirect hop to a phishing or malware page. (location: page.html (empty), page-text.txt (empty))
hidden content
TLS connection failed (connected=false, cert_valid=false, san_match=false) for ivanticloud.com. A domain mimicking a major security vendor that cannot establish a valid TLS session is suspicious — it may be intentionally avoiding TLS inspection, operating on alternate ports, or using non-standard delivery mechanisms to evade security scanning while still serving malicious content to targeted victims. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/ivanticloud.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ivanticloud.com currently scores 42/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.