context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
Domain uses a .biz TLD with a CDN-impersonating name (rocket-cdn-eu.biz) but TLS connection fails entirely (connected=false, cert_valid=false). A CDN domain that cannot establish a valid TLS session is highly anomalous and indicative of a misconfigured phishing/redirect infrastructure or a domain parked for malicious redirection without a functional HTTPS endpoint. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The domain 'rocket-cdn-eu.biz' mimics the naming convention of legitimate CDN providers (e.g., Cloudflare, Fastly, CDN77) by combining a energetic brand term ('rocket'), a geographic qualifier ('eu'), and the word 'cdn'. This pattern is commonly used to impersonate CDN infrastructure to deceive users, developers, or AI agents into trusting the domain as a legitimate content delivery network. The use of .biz rather than .com or a country-code TLD further suggests deceptive intent. (location: metadata.json: domain=rocket-cdn-eu.biz)
social engineering
The domain name construction (rocket-cdn-eu.biz) is designed to convey technical legitimacy and geographic specificity ('eu' for Europe), a classic social engineering pattern to build false trust with technically-oriented targets such as developers or automated systems/AI agents that may whitelist or trust CDN domains by name pattern. (location: metadata.json: domain=rocket-cdn-eu.biz)
hidden content
The page HTML and visible text are completely empty (page.html and page-text.txt are zero bytes), yet the domain resolves and has a WHOIS record. An empty page with no content on a CDN-impersonating domain is consistent with a cloaked site that serves different content based on user-agent, referrer, or IP geolocation — a common technique to hide malicious payloads from scanners while delivering them to real victims. (location: page.html (0 bytes), page-text.txt (0 bytes))
curl https://api.brin.sh/domain/rocket-cdn-eu.bizCommon questions teams ask before deciding whether to use this domain in agent workflows.
rocket-cdn-eu.biz currently scores 48/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.