context safety score
A score of 48/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 page hosted on lenzmx.com contains a meta refresh tag that immediately redirects visitors (content='0; URL=https://www.mobvista.com/cn') to a completely different domain (mobvista.com). The scanned URL is lenzmx.com but the page impersonates and redirects to mobvista.com, suggesting lenzmx.com is acting as a redirect intermediary or parked/hijacked domain funneling traffic to another site. (location: page.html:9 - <meta http-equiv='refresh' content='0; URL=https://www.mobvista.com/cn'>)
brand impersonation
The page hosted on lenzmx.com fully reproduces the branding, content, logo, and identity of Mobvista (广州汇量信息科技有限公司), a legitimate Chinese ad-tech company (HK:01860), including their logo, taglines, statistics, copyright notice, and Chinese ICP filing number. The domain lenzmx.com has no apparent affiliation with Mobvista, indicating the site is impersonating the Mobvista brand. (location: page.html:2,29-31,85 - saved from mobvista.com comment, Mobvista logo, Copyright 2023 Mobvista)
hidden content
The HTML comment at the top of the page explicitly states 'saved from url=(0028)https://www.mobvista.com/cn/' — a hallmark of locally-saved or cloned pages being re-served from a different domain. The page also contains a hidden div element (position: absolute; top: -10000px; width: 0px; height: 0px) used to hide content from view, and a robots meta tag set to 'noindex, nofollow' to prevent search engine indexing and crawling, which is a common tactic to avoid detection while still serving the page to users or bots. (location: page.html:2,8,69-71 - saved-from comment, noindex/nofollow meta, off-screen hidden div)
social engineering
The page presents itself as a legitimate, established Chinese technology company (Mobvista/汇量科技) complete with corporate statistics (10,000+ active developers, 200B+ daily ad requests, 17 global offices), corporate branding, and regulatory filings (ICP license, public security registration). This creates a false sense of legitimacy and trustworthiness for a page being served from an unrelated domain (lenzmx.com), which could be used to deceive users or automated agents into trusting the site. (location: page.html:43-65, page-text.txt:20-41 - corporate statistics and legitimacy signals)
curl https://api.brin.sh/domain/lenzmx.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
lenzmx.com currently scores 48/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.