context safety score
A score of 55/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 (coraline-ost-2009-bruno-coulais.hydr0.org) is a subdomain that clones content from mp3.cc, with a canonical tag pointing to mp3.cc and all navigation links redirecting to mp3.cc. The subdomain appears to be a shadow/mirror site operated by the same entity (hydr0.org), intercepting traffic searching for the Coraline OST and funneling users through a third-party proxy domain rather than the legitimate mp3.cc site. (location: page.html:9 - canonical href and all internal links point to mp3.cc while page is served from hydr0.org subdomain)
malicious redirect
All audio file URLs route through 'fine.sunproxy.net', a third-party proxy/intermediary domain, using base64-encoded file path parameters. This proxy intercepts all media download traffic, allowing the sunproxy.net operator to log user activity, substitute files, or serve malware instead of legitimate MP3 files. The use of a proxy for all 19+ audio files is deliberate infrastructure for traffic interception. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570 - all data-url attributes point to fine.sunproxy.net)
brand impersonation
The page fully impersonates mp3.cc — reproducing its logo, branding, layout, genre navigation, footer copyright notice ('© 2017–2026 MP3.cc'), and all UI elements — while being served from the unrelated domain coraline-ost-2009-bruno-coulais.hydr0.org. Users and AI agents browsing or scraping this page would believe they are on the legitimate mp3.cc service. (location: page.html:5,11,33-36,590,595 - title, og:site_name, logo, footer all assert MP3.cc identity)
hidden content
The 12 suspicious base64 blobs flagged in pre-scan context correspond to the base64-encoded file path segments embedded in all fine.sunproxy.net audio URLs (e.g. 'NDgwdkFuTUxJZ0tH...'). While these decode to file path tokens rather than executable payloads, the encoding obscures the actual file paths and proxy routing parameters from casual inspection, hindering analysis of what files are being served. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes containing base64 path segments in fine.sunproxy.net URLs)
curl https://api.brin.sh/domain/coraline-ost-2009-bruno-coulais.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
coraline-ost-2009-bruno-coulais.hydr0.org currently scores 55/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.