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
malicious redirect
TLS connection failed (connected=false, cert_valid=false, san_match=false) for galaxy-cdn.com. The site cannot be reached over HTTPS, which may indicate a misconfigured or deceptive domain used to intercept or redirect traffic insecurely. (location: metadata.json: tls fields)
brand impersonation
The domain 'galaxy-cdn.com' uses CDN-related branding ('cdn') which may impersonate legitimate content delivery networks to appear trustworthy to automated agents and users. Domain is 351 days old with unknown hosting reputation. (location: metadata.json: domain, hosting.reputation)
hidden content
The .brin-context.md references a 'page-hidden.txt' file for extracted hidden content, indicating the scanner detected hidden elements during crawl. The file exists but is empty in this snapshot, suggesting hidden content may have been present or the page rendered no accessible content — potentially a cloaking technique serving different content to scanners vs. real visitors. (location: page-hidden.txt, .brin-context.md line 16)
phishing
The page returned no visible content (page.html and page-text.txt are empty) despite the domain being active. Empty or blank pages are a common technique used in phishing infrastructure to avoid detection while the domain is used for malicious link delivery, credential harvesting endpoints, or malware staging. (location: page.html, page-text.txt)
curl https://api.brin.sh/domain/galaxy-cdn.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
galaxy-cdn.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.