context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
The page is a Zimbra Web Client Sign In page hosted on a third-party domain (zcs.silomanagement.gr) that is unaffiliated with Zimbra/Synacor. The login form posts credentials to '/' on this domain, meaning any entered username and password are submitted to an attacker-controlled server rather than a legitimate Zimbra instance. (location: page.html:44 — <form id="zLoginForm" method="post" action="/">)
credential harvesting
The login form collects both username and password fields and submits them via HTTP POST to the root path of the attacker-controlled domain zcs.silomanagement.gr. The form includes autocomplete="off" on the password field and a CSRF token, consistent with a functional credential capture mechanism rather than a simple static clone. (location: page.html:44-63 — form fields for username and password with POST action)
brand impersonation
The page fully impersonates Zimbra Collaboration Suite, copying its official login UI including the Zimbra logo banner (linking to www.zimbra.com), copyright notice ('Copyright © 2005-2023 Synacor, Inc. All rights reserved. "Zimbra" is a registered trademark of Synacor, Inc.'), and the authentic skin/JS codebase. This is designed to deceive users into believing they are on a legitimate Zimbra server. (location: page.html:24,40,99 — title, banner link, and footer copyright)
social engineering
The page uses the full visual and functional appearance of a trusted enterprise email login page (Zimbra) to create a false sense of legitimacy. The inclusion of 'Stay signed in' checkbox, 'Web App Version' selector, and familiar Zimbra UI elements are deliberate social engineering tactics to lower user suspicion and encourage credential entry. (location: page.html:65-90 — Stay signed in checkbox and Web App Version UI elements)
curl https://api.brin.sh/domain/zcs.silomanagement.grCommon questions teams ask before deciding whether to use this domain in agent workflows.
zcs.silomanagement.gr 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.