context safety score
A score of 38/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 conditionally redirects based on referrer or user-agent
brand impersonation
The page is served at hosteurope.de but the JavaScript references brand identifiers '123-reg' and '123-reg.co.uk' (a UK hosting brand), and internal API paths use 'heg-cp.com' (HEG = HostEurope Group). The rendered page is empty (no visible content), yet loads full SPA infrastructure. This pattern — a legitimate-looking domain serving content that silently bootstraps under a different brand identity — is consistent with brand impersonation or a cloaked redirect page. (location: page.html:21-25, page.html:44-59)
malicious redirect
A script tag at the end of the body loads an obfuscated external resource from a path that looks randomised/encoded: '/SKsS9m/Eo7ASS/H8sO/CrqToO/le/5Q7DVmrDQ94VJL/ZR4HPEILAQ/DE1/DIht6E04B'. This path does not match the structured naming of the other static assets (/pex-static/...) and has the hallmarks of a tracking pixel, redirect script, or malicious payload injected into the page. (location: page.html:72)
obfuscated code
The script src '/SKsS9m/Eo7ASS/H8sO/CrqToO/le/5Q7DVmrDQ94VJL/ZR4HPEILAQ/DE1/DIht6E04B' uses a heavily obfuscated, non-semantic URL path inconsistent with all other asset paths on the page. This is a strong indicator of obfuscated or injected malicious code, potentially a skimmer, exfiltration script, or command-and-control beacon. (location: page.html:72)
hidden content
The page renders no visible text content whatsoever (page-text.txt is effectively empty, page-hidden.txt is empty). The entire page is a JavaScript SPA shell with an empty <div id='root'>. This blank-page pattern is used to hide malicious activity from human visitors while executing scripts silently, and may also be used to serve different content to bots or AI agents versus human browsers. (location: page.html:69, page-text.txt)
social engineering
The TLS certificate expires in only 16 days (days_until_expiry: 16) while the domain is 39 years old (14364 days). A long-lived legitimate domain would typically have auto-renewing certificates. An expiring cert on an otherwise established domain may indicate the domain has changed hands, been compromised, or is being used temporarily for a campaign. (location: metadata.json:tls.days_until_expiry)
prompt injection
The bootstrap API call at '/api/hug/api/v1/bootstrap' dynamically injects configuration data (window.hugBootstrap) into the page environment. If this endpoint returns attacker-controlled content, it could inject instructions targeting AI agents or browser automation that consume the page's DOM or data context. (location: page.html:44-59)
curl https://api.brin.sh/domain/hosteurope.deCommon questions teams ask before deciding whether to use this domain in agent workflows.
hosteurope.de currently scores 38/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.