context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
social engineering
Domain 'eromecdn.com' is only 36 days old (extremely new). Newly registered domains mimicking CDN infrastructure ('cdn' suffix) are a common pattern for malicious actors setting up short-lived infrastructure for phishing, malware distribution, or credential harvesting campaigns before being taken down. (location: metadata.json: whois.domain_age_days=36, domain=eromecdn.com)
brand impersonation
The domain 'eromecdn.com' appends 'cdn' to suggest it is a content delivery network or legitimate infrastructure provider. This naming pattern is commonly used to impersonate or piggyback on the reputation of CDN services, potentially deceiving users or automated systems into trusting the domain. (location: metadata.json: domain=eromecdn.com)
hidden content
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for an HTTPS URL. The page HTML and visible text are both empty, meaning no content was retrievable. A domain that serves no content over HTTPS but exists may be in a pre-activation or covert operational phase — used for tracking pixels, redirect chaining, or as a command-and-control staging domain not yet indexed or monitored. (location: metadata.json: tls.connected=false, tls.cert_valid=false; page.html (empty); page-text.txt (empty))
malicious redirect
The combination of a very new domain (36 days), a CDN-style name, no TLS, and no visible content is consistent with a redirect or pass-through infrastructure node. Such domains are frequently used as intermediate hops in redirect chains to obscure the final malicious destination from URL scanners and reputation systems. (location: metadata.json: domain=eromecdn.com, domain_age_days=36, tls.connected=false)
curl https://api.brin.sh/domain/eromecdn.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
eromecdn.com currently scores 44/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.