context safety score
A score of 47/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page at hisense.com displays a Chinese-language security block page ('您的请求可能存在威胁，已被拦截！') rather than the legitimate Hisense brand website. The rendered content does not match the expected legitimate brand presence, indicating the domain may be serving a WAF/security-vendor interception page that impersonates or replaces the real brand content, potentially misleading users about the site's legitimacy. (location: page-text.txt:1, page.html:1)
hidden content
The page-text.txt contains inline obfuscated JavaScript bundle code embedded within what should be visible page text. The script dynamically injects content (event_id, TYPE, timestamp) by traversing DOM comment nodes, which is a technique used to hide data from static analysis. The JavaScript reads from HTML comment nodes to extract event metadata, obscuring the page's true behavior from passive inspection. (location: page-text.txt:1)
obfuscated code
The visible text layer contains a minified/obfuscated webpack JavaScript bundle that dynamically manipulates the DOM at runtime. The code uses comment node traversal (nodeType==8) to extract hidden parameters ('event_id', 'TYPE') from the HTML source, a technique characteristic of obfuscated tracking or exfiltration logic that evades static content scanners. (location: page-text.txt:1)
prompt injection
The page content delivered to an AI agent scraping hisense.com contains Chinese-language instructions ('如存在错误拦截，请联系网站管理员并提供 Event ID') embedded alongside executable JavaScript. This pattern — human-readable instructions mixed with code in the text layer — could be leveraged as a prompt injection vector targeting AI agents that parse page-text.txt as trusted content, potentially directing agent behavior (e.g., contacting an attacker-controlled admin endpoint with an Event ID). (location: page-text.txt:1)
curl https://api.brin.sh/domain/hisense.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hisense.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.