context safety score
A score of 59/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 scanned domain (chicane-feat-moya-brennan-saltwater-sebastien-remix.hydr0.org) is a subdomain that impersonates and proxies content from mp3.cc, a third-party music download site. The canonical URL, all asset URLs, and all internal links point to mp3.cc rather than the hosting domain, indicating the subdomain acts as a redirect/proxy front for mp3.cc content. The pre-scan context confirms 1 redirect was detected. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/...">)
brand impersonation
The subdomain hydr0.org hosts a page that fully replicates MP3.cc branding, layout, title tags, and OG metadata. The site presents itself as MP3.cc (logo, copyright '© 2017–2026 MP3.cc', og:site_name 'MP3.cc') while operating under a different domain (hydr0.org), constituting brand impersonation of mp3.cc. (location: page.html:5,11,671 - title tag, og:site_name, footer copyright)
malicious redirect
All audio file URLs in the playlist use the third-party proxy domain fine.sunproxy.net containing long Base64-encoded path components. This is consistent with obfuscated proxy routing of media files through an intermediary server, potentially used for tracking, ad injection, or delivering malicious payloads alongside media. The 12 suspicious base64 blobs flagged in the pre-scan correspond to these encoded media URLs. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes on playlist-play anchors)
social engineering
The site offers free MP3 downloads ('Download mp3 free, listen music online') of copyrighted music (Chicane feat. Moya Brennan tracks) via a domain that proxies mp3.cc. This lures users to interact with a potentially untrustworthy third-party domain under the guise of a legitimate music service, a common social engineering tactic to drive traffic and potentially expose users to further threats through the proxy infrastructure. (location: page.html:5 - title tag; page.html:228-661 - playlist download links via fine.sunproxy.net)
curl https://api.brin.sh/domain/chicane-feat-moya-brennan-saltwater-sebastien-remix.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
chicane-feat-moya-brennan-saltwater-sebastien-remix.hydr0.org currently scores 59/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.