context safety score
A score of 67/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 URL (bruno-coulais-the-children-s-choir-of-nice-ost-coraline.hydr0.org) is a subdomain that mirrors content from mp3.cc, with all canonical links, CSS, JS, and internal navigation pointing to mp3.cc. The page is a shadow/proxy copy of mp3.cc served from a different domain (hydr0.org), constituting an off-brand redirect/proxying arrangement. One redirect was flagged in the pre-scan context. (location: <link rel="canonical" href="https://mp3.cc/..."> and all internal links; page.html:9)
brand impersonation
The site at hydr0.org impersonates or mirrors mp3.cc by reproducing its full UI, branding, logo, and content under a different domain. The page title, OG metadata, footer copyright, and all navigation links reference mp3.cc while being served from hydr0.org. This is a brand impersonation pattern where a third-party domain serves a replica of a legitimate site. (location: page.html:5,9,11-14,609-614)
malicious redirect
All MP3 audio file URLs use the third-party proxy domain fine.sunproxy.net with base64-encoded path parameters (e.g., NDgwdkFuTUxJZ0tHbEJUVFE0...). Audio streams are routed through an opaque proxy with obfuscated file paths rather than served directly, raising concerns about traffic interception, tracking, or malware delivery via media files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 (all data-url attributes))
hidden content
MP3 filenames embedded in the fine.sunproxy.net URLs contain the tag '(Hydr0.org)' appended to each filename (e.g., Bruno_Coulais_-_coraline_(Hydr0.org).mp3). This watermarking of pirated content in filenames is embedded within base64-encoded URL parameters and is not visible to end users, indicating tracking or attribution obfuscation. (location: page.html:228,247,266 (and all data-url data attributes referencing fine.sunproxy.net))
social engineering
The site offers free MP3 downloads of copyrighted music (Coraline OST by Bruno Coulais) without authorization, which is a common lure used to attract users to piracy/shadow-proxy sites. Such sites typically monetize through ads, data collection, or malware delivery. The contact email hydrofm@yandex.com (Yandex, Russian email provider) in the footer is associated with the site operator and is not affiliated with mp3.cc's legitimate operators. (location: page.html:614; page-text.txt:517)
curl https://api.brin.sh/domain/bruno-coulais-the-children-s-choir-of-nice-ost-coraline.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bruno-coulais-the-children-s-choir-of-nice-ost-coraline.hydr0.org currently scores 67/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.