context safety score
A score of 65/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
Page is served from eh-de-spag-heddy.hydr0.org but fully impersonates MP3.cc: the title tag reads 'MP3.cc', the logo and header branding display 'MP3.cc', the canonical link points to mp3.cc, og:site_name is 'MP3.cc', and all navigation links go to mp3.cc. This is an unauthorized mirror/clone of the MP3.cc brand operating under a different domain. (location: page.html:5 (title), page.html:9 (canonical), page.html:11 (og:site_name), page.html:33-36 (logo), page.html:614 (copyright footer))
malicious redirect
The site serves on eh-de-spag-heddy.hydr0.org with 1 detected redirect (per Tier 2 scan). The canonical URL and all internal links redirect users to mp3.cc, making the hydr0.org domain act as a transparent proxy that intercepts and re-serves MP3.cc content. Audio files are proxied through fine.sunproxy.net rather than served from legitimate MP3.cc infrastructure. (location: metadata.json (redirects: 1), page.html:9 (canonical redirect target), all data-url attributes pointing to fine.sunproxy.net)
obfuscated code
All 20 audio file URLs use double-encoded base64 tokens hosted at fine.sunproxy.net/file/. Each token decodes to a further base64 string that then decodes to binary encrypted data, obfuscating the actual file endpoints. This multi-layer encoding is used to hide the piracy proxy infrastructure serving copyrighted MP3 files and to prevent easy identification or blocking of the content delivery mechanism. The filenames embedded in the URLs include '(Hydr0.org)' branding, confirming deliberate association with the hydr0.org piracy network. (location: page.html lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589 (all data-url attributes))
curl https://api.brin.sh/domain/eh-de-spag-heddy.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
eh-de-spag-heddy.hydr0.org currently scores 65/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.