context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The domain kmail-lists.com is serving the full Klaviyo homepage (klaviyo.com) — complete with Klaviyo branding, logos, meta tags, og:url pointing to www.klaviyo.com, and canonical link to www.klaviyo.com — from an unaffiliated third-party domain. The domain name 'kmail-lists' mimics Klaviyo's product identity ('K' prefix, 'mail', 'lists') while impersonating the legitimate klaviyo.com site. (location: domain: kmail-lists.com; og:url and canonical both set to https://www.klaviyo.com; page.html line 1)
phishing
The page hosts a functional email sign-up form (id='form--demoRequest') that collects email addresses from users who believe they are on the legitimate Klaviyo website. Visitors reaching kmail-lists.com via a misleading link would submit their email to an uncontrolled third party while believing they are signing up with Klaviyo. (location: page.html line 180: <form action='#' id='form--demoRequest'>, input name='email')
credential harvesting
The page includes a 'Log in' / 'Customer Login' link rendered as part of the spoofed Klaviyo interface. Users who navigate to login from this impersonator domain could have credentials intercepted. The login link href points to https://www.klaviyo.com/login within the page content, but the serving domain is kmail-lists.com, creating a deceptive trust context. (location: page.html line 178: <a href='https://www.klaviyo.com/login'>Customer Login</a>; page-text.txt line 18)
malicious redirect
The page loads a Gatsby redirect template component ('component---packages-gatsby-theme-marketing-src-templates-redirect-index-tsx') suggesting redirect infrastructure is present. Combined with the domain mismatch, this could be used to silently redirect users to the legitimate klaviyo.com after harvesting data, obscuring the deception. (location: page-text.txt line 39: window.___chunkMapping includes 'redirect-index-tsx')
hidden content
A navigation list with display:none is present at the top of the body, containing 17 internal Klaviyo links. While this pattern is sometimes used for accessibility or SEO purposes, on an impersonator domain it also contributes to search-engine indexing of Klaviyo content under a fraudulent domain, amplifying brand confusion and discoverability. (location: page.html line 161-178: <div style='display:none'><ul> with 17 Klaviyo navigation links)
curl https://api.brin.sh/domain/kmail-lists.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kmail-lists.com currently scores 36/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.