context safety score
A score of 63/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
malicious redirect
The page is hosted at alan-walker-marshmello-style.hydr0.org but all canonical links, CSS, JS, images, and navigation point to mp3.cc. The subdomain acts as a cloaked mirror/redirect front for mp3.cc, potentially used to bypass blocklists or drive traffic through an unvetted intermediary domain while impersonating the legitimate service. (location: page.html:9 - canonical href and all asset/nav links point to mp3.cc)
brand impersonation
The page impersonates the legitimate mp3.cc service by cloning its full UI (logo, navigation, music player, footer copyright) and serving it from a third-party subdomain (hydr0.org) without authorization. The footer contact email hydrofm@yandex.com and the Hydr0.org branding embedded in all MP3 filenames suggests this is an unofficial mirror monetizing or redirecting traffic under the guise of a known brand. (location: page.html:5,329 - title and footer show MP3.cc branding; filenames in data-url attributes contain (Hydr0.org))
malicious redirect
All audio file download/play URLs route through fine.sunproxy.net, a third-party proxy service, rather than directly through mp3.cc infrastructure. The base64-encoded path parameters in these URLs obscure the true destination and could be used to redirect users to malicious payloads or track/exfiltrate user behavior. The 5 suspicious base64 blobs flagged in Tier 2 correspond to these encoded file URLs. (location: page.html:228,247,266,285,304 - data-url attributes pointing to fine.sunproxy.net with base64-encoded paths)
hidden content
The page sets meta robots to 'noarchive', preventing search engine caching. Combined with the subdomain structure and third-party proxying, this is consistent with a site designed to avoid archival and forensic scrutiny while serving content that mirrors a legitimate service. (location: page.html:8 - <meta name="robots" content="noarchive">)
curl https://api.brin.sh/domain/alan-walker-marshmello-style.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
alan-walker-marshmello-style.hydr0.org currently scores 63/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.