context safety score
A score of 45/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
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
The page immediately redirects all visitors to https://com-x.life/ via window.location.replace() after completing a bot-detection fingerprinting check. The redirect destination is encoded as a URL-encoded string (decodeURIComponent('https%3A%2F%2Fcom-x.life%2F')) to obscure the target from static scanners. The page has no visible content and exists solely as a cloaked redirect gateway. (location: page.html:28, page.html:44-46)
obfuscated code
The page contains an obfuscated JavaScript payload that performs browser fingerprinting before redirecting. It collects navigator.webdriver (bot detection), touch capabilities, screen resolution/color depth, WebCrypto API availability, and RAF support. This data is POSTed to the server endpoint '/_v' with a base64-encoded token before allowing the redirect to proceed. The token 'MzQuOTYuNDUuMjQxfDE3NzI2MzczNzl8MXw2NTgxODN8NTQ0MmFiMDc0MGMxZTIzNjI4NGZmZDZkMTE2M2JmN2Y=' decodes to fingerprinting session data including an IP address (34.96.45.241) and timestamp. CSS class names are randomized (x12394, x34549, x84006, x20247) to hinder pattern detection. (location: page.html:23-145)
hidden content
The page renders no visible text content to users or crawlers — only an animated loading spinner. All meaningful activity occurs silently in JavaScript. The meta tag 'robots: noindex,nofollow' explicitly instructs search engines to ignore the page, suggesting intentional evasion of indexing and analysis. The page title is also empty. (location: page.html:5, page.html:7, page.html:18-22)
social engineering
The page displays a fake loading spinner and progress bar animation (CSS classes x34549, x84006, x20247) to deceive visitors into believing a legitimate page is loading while covert fingerprinting and redirection occurs in the background. This creates a false sense of normal page behavior to mask the underlying malicious activity. (location: page.html:10-16, page.html:19-22)
prompt injection
The TLS certificate has only 8 days until expiry (days_until_expiry: 8), which is anomalously short and may indicate the infrastructure is temporary or disposable — consistent with short-lived threat actor infrastructure designed to operate briefly before abandonment. Combined with the bot-detection and redirect chain, this suggests a transient malicious redirect gateway. (location: metadata.json:1)
curl https://api.brin.sh/domain/com-x.lifeCommon questions teams ask before deciding whether to use this domain in agent workflows.
com-x.life currently scores 45/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.