context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The page is served from mobirise.info (a .info TLD) but fully impersonates the legitimate mobirise.com brand, displaying the official Mobirise logo, trademark notice, and all branding assets loaded directly from mobirise.com. The domain mobirise.info is not the official Mobirise domain (mobirise.com), creating a typosquat/lookalike scenario where users believing they are on the official site may be deceived. (location: page.html: <base href>, logo img src, footer trademark text; metadata.json: domain=mobirise.info vs displayed brand mobirise.com)
malicious redirect
The canonical URL and all hreflang alternate links point to cu3ox.com, a completely different domain unrelated to either mobirise.info or mobirise.com. All navigation dropdown links also redirect to cu3ox.com. This systematically funnels visitors from mobirise.info to cu3ox.com, an unknown third-party domain, potentially for SEO manipulation, affiliate fraud, or further redirection to malicious content. (location: page.html line 38: <link rel='canonical' href='https://cu3ox.com/ai-website-generator.html'>; lines 74-115: all dropdown nav links pointing to cu3ox.com)
hidden content
A large block of keyword-stuffed SEO spam text is hidden from users via inline style 'display:none'. The hidden text contains over 40 AI/web-builder keyword phrases designed to manipulate search engine rankings without being visible to human visitors. This is a black-hat SEO cloaking technique. (location: page.html line 178: <span class='display-7' style='display:none'> Generate e a website with automated website creator, ai web builder, intelligent site generator...)
hidden content
Navigation dropdown menus are rendered with style='display: none;' hiding two sets of links — one set pointing to cu3ox.com and another to mobirise.com — from casual visual inspection. These hidden menus serve SEO link injection purposes while remaining invisible to users. (location: page.html lines 70-117: <div class='dropdown-menu' style='display: none;'> and lines 133-135: <div class='lang-dropdown-menu' style='display:none;'>)
curl https://api.brin.sh/domain/mobirise.infoCommon questions teams ask before deciding whether to use this domain in agent workflows.
mobirise.info 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.