context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page uses meta refresh redirect
malicious redirect
The root page immediately redirects to /campaigns/login.do via a meta http-equiv refresh with a 0-second delay. The domain name 'maillist-manage.com' mimics the appearance of a legitimate email list management service, and the silent, instantaneous redirect to a login page is a common phishing and credential-harvesting pattern used to funnel visitors to a fake authentication portal without any user-visible content. (location: page.html:2 — <meta http-equiv="refresh" content="0;url=/campaigns/login.do">)
brand impersonation
The domain 'maillist-manage.com' is a generic-sounding name that closely mimics the naming conventions of legitimate email marketing and list management platforms (e.g., Mailchimp, Mailjet, Constant Contact). Combined with the redirect to /campaigns/login.do, this pattern is consistent with impersonating a known SaaS brand to harvest credentials from users who believe they are logging into a trusted service. (location: metadata.json — domain: maillist-manage.com)
credential harvesting
The site presents no visible content and immediately redirects all visitors to a /campaigns/login.do endpoint. This login-page-only structure with no explanatory content, branding, or navigation is a hallmark of a credential harvesting page designed to capture usernames and passwords. The TLS certificate is a low-assurance DV cert from Let's Encrypt (expiring in 31 days), consistent with a short-lived phishing infrastructure. (location: page.html:2 and metadata.json — tls.days_until_expiry: 31, redirect target: /campaigns/login.do)
phishing
The combination of a deceptive domain name mimicking email service providers, an immediate silent redirect to a login page, a DV TLS certificate expiring in 31 days, and unknown hosting reputation are collectively consistent with a phishing site. The hosting reputation is listed as 'Unknown', which is typical of newly spun-up or deliberately obscured phishing infrastructure. (location: metadata.json — hosting.reputation: Unknown; page.html:2 — meta refresh redirect)
curl https://api.brin.sh/domain/maillist-manage.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
maillist-manage.com currently scores 40/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.