context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is saved from http://www.jovetech.com/ (as indicated by the IE saved-page comment '<!-- saved from url=(0024)http://www.jovetech.com/ -->') but is being served at jovcloud.com. The content also references http://webcc.jovecloud.com/Default.aspx as a web control endpoint, creating a cross-domain trust confusion between jovcloud.com and jovetech.com. (location: page.html:2 - saved-from comment; page-text.txt:7 - jovecloud.com URL reference)
brand impersonation
The domain jovcloud.com closely resembles jovecloud.com (referenced within the page content) and jovetech.com (the original saved-from URL). The page content directs users to install browser controls from http://webcc.jovecloud.com/Default.aspx, a different domain, while the current serving domain is jovcloud.com. This typosquat-style domain mismatch could deceive users into trusting jovcloud.com as if it were the legitimate jovecloud.com or jovetech.com service. (location: page.html:2; page-text.txt:7 - reference to jovecloud.com and jovetech.com)
hidden content
The page contains approximately 30 blank lines between the main content div and the footer (lines 281-310 of page.html), which is an unusual structural pattern that may be used to hide content from casual inspection or push visible content out of viewport. Additionally, TLS is not connected/valid for this site despite it being served over HTTPS according to metadata, meaning content integrity cannot be verified. (location: page.html:280-313 - large blank region between content and footer)
social engineering
The page instructs users to install a browser page control ('第一次使用需安装页面控件' - 'first time use requires installing page controls') from an external URL (http://webcc.jovecloud.com/Default.aspx). Prompting users to install browser plugins or ActiveX controls from a site with mismatched domain identity and no valid TLS is a social engineering vector for delivering malicious software. (location: page-text.txt:7 - install control instruction with external URL reference)
curl https://api.brin.sh/domain/jovcloud.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
jovcloud.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.