context safety score
A score of 40/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
malicious redirect
Page immediately redirects all visitors via JavaScript window.location.replace() to a tracking URL appended with a browser fingerprint ID. A 300ms timeout fallback ensures redirection even if fingerprinting fails. This is a classic cloaking/traffic distribution system (TDS) pattern used to route victims to phishing or malware pages while evading automated scanners. (location: page.html:6-26)
hidden content
A hidden anchor link (<div style='display: none;'>) points to the same tracking redirect URL with fp=-3, making it invisible to users but potentially crawlable. This is used to support the redirect infrastructure while concealing it from the visible page. (location: page.html:32)
hidden content
A <noscript> meta-refresh redirect is present, targeting the same tracking URL with fp=-5. This ensures users without JavaScript are also silently redirected, leaving no visible content for the user to inspect. (location: page.html:33 / page-text.txt:3)
obfuscated code
The page loads an external fingerprinting library (FingerprintJS via /js/fingerprint/iife.min.js) to collect a unique visitor ID before redirecting. The fingerprint is appended to the redirect URL as a tracking parameter (fp=<visitorId>), enabling victim profiling and selective targeting — a hallmark of phishing kit infrastructure. (location: page.html:4,18-23)
social engineering
The only visible text on the page is 'Click here to enter' inside a hidden div, providing a deceptive call-to-action that is hidden from users but may be used to lure automated crawlers or as a fallback lure. The page title 'webstuhlmanufaktur.com' does not match the subdomain, creating brand confusion. (location: page.html:32 / page-text.txt:2)
brand impersonation
The subdomain 'userallmanager-comptemaincloud.webstuhlmanufaktur.com' uses misleading keywords ('userallmanager', 'comptemain', 'cloud') that suggest account management or cloud service portals, potentially impersonating enterprise SaaS or cloud providers. The page title shows 'webstuhlmanufaktur.com' (a furniture manufacturer domain), indicating the legitimate domain has been hijacked or its subdomain abused. (location: metadata.json:1 / page.html:3)
curl https://api.brin.sh/domain/userallmanager-comptemaincloud.webstuhlmanufaktur.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
userallmanager-comptemaincloud.webstuhlmanufaktur.com currently scores 40/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.