context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on a subdomain of hydr0.org (alan-walker-don-t-you-hold-me-down-el.hydr0.org) but all canonical links, CSS, JS, and navigation point to mp3.cc. The canonical tag explicitly redirects crawlers and agents to https://mp3.cc/t/790725953-alan-walker-don-t-you-hold-me-down-el/. This subdomain acts as a redirect/mirror layer that launders traffic from hydr0.org to mp3.cc, bypassing direct navigation to the legitimate domain. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/790725953-alan-walker-don-t-you-hold-me-down-el/">)
brand impersonation
The site impersonates MP3.cc by fully mirroring its branding, logo, CSS, JavaScript, and UI — all loaded directly from mp3.cc's servers — while being served from the unrelated domain hydr0.org. The page title, metadata, og:site_name, and footer all claim to be 'MP3.cc' while the actual serving domain is a third-party subdomain. Users and agents navigating to this URL would believe they are on the legitimate MP3.cc site. (location: page.html:5,11,500 - title, og:site_name, footer copyright)
malicious redirect
All audio file URLs use the proxy domain fine.sunproxy.net to serve MP3 files. These are obfuscated URLs with long base64-encoded path segments (12 suspicious base64 blobs flagged by Tier 2). Users downloading files are routed through an unaffiliated third-party proxy (sunproxy.net) rather than the legitimate content source, enabling potential traffic interception, content substitution, or tracking. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475 - data-url attributes pointing to fine.sunproxy.net)
hidden content
The 12 suspicious base64 blobs flagged in Tier 2 correspond to the encoded path segments in the fine.sunproxy.net file URLs. While these appear to be encoded file paths rather than injected payloads, they obscure the true destination of audio downloads and prevent users or agents from inspecting the actual resource being fetched. (location: page.html - data-url attributes with base64-encoded segments, e.g. line 228: NDgwdkFuTUxJZ0tHbEJUVFE0QUZzNUtmT3Q5UlZlNlAveTNlSGJkYkhO...)
social engineering
The deceptive link flagged in Tier 2 corresponds to the 'Online Radio' sidebar link pointing to https://looz.net/ — a completely off-domain third-party site presented inline within what appears to be the MP3.cc navigation, styled identically to legitimate genre navigation links. This could mislead users into believing looz.net is a feature of MP3.cc. (location: page.html:204 - <a href="https://looz.net/" class="z__important no-ajax" target="_blank">Online Radio</a>)
curl https://api.brin.sh/domain/alan-walker-don-t-you-hold-me-down-el.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
alan-walker-don-t-you-hold-me-down-el.hydr0.org currently scores 41/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.