context safety score
A score of 56/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-white-america-bass.hydr0.org but all canonical links, CSS, JS, and navigation point to mp3.cc. The subdomain acts as a shadow/mirror host funneling traffic to mp3.cc, with a recorded redirect (Tier 1: Redirects: 1). The actual serving domain hydr0.org is separate from the branded mp3.cc domain users would expect. (location: metadata.json: url=https://eminem-white-america-bass.hydr0.org; page.html line 9: canonical href=https://mp3.cc/t/3778204743-eminem-white-america-bass/)
brand impersonation
The site presents itself visually and structurally as MP3.cc (logo, CSS, JS, footer copyright all reference mp3.cc) while being served from the unrelated domain hydr0.org. This impersonates the MP3.cc brand to lend legitimacy to a third-party host, potentially deceiving users about which service they are actually using. (location: page.html lines 5, 9, 11-14, 18-19, 33-36, 652: all brand references point to mp3.cc while actual host is hydr0.org)
malicious redirect
All MP3 audio files are served through fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc or hydr0.org. File URLs are encoded with long base64-like tokens (matching the 12 suspicious base64 blobs flagged in Tier 2). Users clicking play are routed through this opaque proxy, which could intercept traffic, serve malware, or track users without their knowledge. (location: page.html lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589, 608: data-url attributes pointing to fine.sunproxy.net/file/)
hidden content
The deceptive link flagged in Tier 2 (deceptive link count: 1) corresponds to the 'Online Radio' sidebar link pointing to https://looz.net/ with class 'z__important', which navigates users away from the current site to an entirely different domain with no contextual warning. The link text does not indicate an off-site redirect. (location: page.html line 204: <a href="https://looz.net/" class="z__important no-ajax" target="_blank">Online Radio</a>)
curl https://api.brin.sh/domain/eminem-white-america-bass.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
eminem-white-america-bass.hydr0.org currently scores 56/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.