context safety score
A score of 50/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The domain alan-walker-elley-duhe.hydr0.org redirects to mp3.cc content (canonical tag points to https://mp3.cc/t/4084669929-alan-walker-elley-duhe/, all assets load from mp3.cc). The subdomain hydr0.org is used as a proxy/mirror for mp3.cc, which is a known MP3 piracy site. The redirect count of 1 was flagged in Tier 2 signals and is confirmed by the canonical URL discrepancy between the serving domain and the declared canonical. (location: page.html:9 - canonical href)
brand impersonation
The site impersonates MP3.cc, a third-party music download service, by mirroring its content and branding (logo, CSS, JS all loaded from mp3.cc) while being served from a different domain (alan-walker-elley-duhe.hydr0.org). The page title and all content present as if the user is on MP3.cc, but the actual serving domain is unrelated. (location: page.html:5 - title tag, line 9 - canonical, line 33 - logo href)
malicious redirect
All MP3 audio files are served via fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc. The file URLs contain long base64-encoded path segments (flagged as 6 suspicious base64 blobs in Tier 2). This routes media downloads through an unknown intermediary that could log, modify, or substitute file content. (location: page.html:228,247,266,285,304,323 - data-url attributes pointing to fine.sunproxy.net)
hidden content
The 6 suspicious base64 blobs in the audio file URLs (data-url attributes) are base64-encoded strings within the fine.sunproxy.net file paths. While these appear to be obfuscated file routing tokens rather than injected payloads, they obscure the true destination of media file downloads from both users and automated scanners. (location: page.html:228 - NDgwdkFuTUxJZ0tH... and similar base64 segments in all 6 playlist-play data-url values)
social engineering
The deceptive link flagged in Tier 2 corresponds to the 'Online Radio' sidebar link pointing to https://looz.net/ with class 'z__important', which is an off-brand external site unrelated to MP3.cc. This link is styled differently (z__important class) and opens in a new tab (_blank), potentially directing users to an unrelated third-party site under the guise of a genre navigation option. (location: page.html:204 - <a href="https://looz.net/" class="z__important no-ajax" target="_blank">)
curl https://api.brin.sh/domain/alan-walker-elley-duhe.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
alan-walker-elley-duhe.hydr0.org currently scores 50/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.