context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Page impersonates Zimbra webmail (a legitimate enterprise email platform) with French-language login UI ('Bienvenue, vous pouvez accéder à vos mails!', 'Email*', 'Mot de pas... Se connecter') hosted on a GoDaddy site-builder subdomain (site-ibqef3p3z.godaddysites.com). The site title and metadata are branded 'wbmail.free', completely unrelated to Zimbra, confirming deliberate impersonation. (location: page-text.txt:1, page.html metadata (title: wbmail.free))
credential harvesting
A fake Zimbra login form solicits email address and password ('Email*', 'Mot de pas...' i.e. 'Mot de passe' / Password) on a non-Zimbra domain. Credentials entered would be captured by the attacker rather than a legitimate Zimbra server. (location: page-text.txt:1)
phishing
The entire page is constructed as a phishing lure: a convincing Zimbra webmail login page served from a throwaway GoDaddy website-builder subdomain (site-ibqef3p3z.godaddysites.com) with no affiliation to any legitimate organisation. Targets French-speaking enterprise users expecting Zimbra access. (location: https://site-ibqef3p3z.godaddysites.com / page.html, page-text.txt)
social engineering
Use of reCAPTCHA branding ('This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply') adds false legitimacy to the fraudulent login page, increasing victim trust and likelihood of credential submission. (location: page-text.txt:1)
brand impersonation
Site title and OG/Twitter metadata are set to 'wbmail.free', a name designed to evoke free webmail services. The favicon/logo image (Capture kl45.PNG) likely displays a Zimbra or webmail logo to reinforce impersonation. The disguised branding contradicts the actual GoDaddy site-builder hosting. (location: page.html:1-10 (meta tags og:title, twitter:title, title element))
curl https://api.brin.sh/domain/site-ibqef3p3z.godaddysites.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
site-ibqef3p3z.godaddysites.com currently scores 47/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.