context safety score
A score of 61/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted at eminem-feat-maj.hydr0.org but all canonical URLs, CSS, JS, and links point to mp3.cc. The subdomain acts as a redirect/proxy layer that serves mp3.cc content under a different domain, constituting a deceptive redirect. The brin-context confirms 1 redirect was detected. (location: page.html:9 - canonical href points to https://mp3.cc/t/3794480979-eminem-feat-maj/ while the serving domain is eminem-feat-maj.hydr0.org)
brand impersonation
The site at hydr0.org fully impersonates the MP3.cc brand: reproducing its logo, CSS, JS, page layout, and all content. Users seeing the page would believe they are on MP3.cc while actually on hydr0.org, a separate domain. This constitutes brand impersonation of MP3.cc. (location: page.html:5 - title 'MP3.cc', line 33 - logo href to mp3.cc, lines 18-19 - external CSS/JS loaded from mp3.cc)
malicious redirect
All MP3 audio files are served via fine.sunproxy.net, a third-party proxy domain. Users clicking play or download are redirected through this proxy, which could intercept traffic, inject content, or track users without their knowledge. The base64-encoded file URLs (12 suspicious blobs flagged) obscure the actual file paths served through this proxy. (location: page.html:228 - data-url attributes pointing to https://fine.sunproxy.net/file/ with base64-encoded paths for all 20 track entries)
curl https://api.brin.sh/domain/eminem-feat-maj.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
eminem-feat-maj.hydr0.org currently scores 61/100 with a caution 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.