context safety score
A score of 73/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 (angel-baby-rosie-the-originals.hydr0.org) redirects to content mirroring mp3.cc, a third-party music download site. The subdomain on hydr0.org is used as a proxy/redirect layer to serve mp3.cc content, obscuring the true origin and potentially bypassing blocklists. The canonical tag and all resource URLs point to mp3.cc while the serving domain is hydr0.org. (location: page.html:9 - canonical href and all internal links point to mp3.cc while page is served from hydr0.org subdomain)
brand impersonation
The page fully impersonates MP3.cc (logo, branding, layout, canonical URLs, copyright notice '© 2017–2026 MP3.cc') while being served from a completely different domain (angel-baby-rosie-the-originals.hydr0.org). This is a domain-level brand impersonation or unauthorized mirror that presents itself as the legitimate MP3.cc service. (location: page.html:5,9,652 - title tag, canonical link, and footer copyright all reference MP3.cc while served from hydr0.org)
malicious redirect
All audio file play URLs route through fine.sunproxy.net, a third-party proxy service not affiliated with the displayed brand (mp3.cc). Audio streams are proxied through an intermediary that could log, modify, or substitute content. The filenames in the proxy URLs embed '(Hydr0.org)' indicating deliberate rebranding of content through this proxy chain. (location: page.html:228,247,266 - data-url attributes on playlist-play anchors point to fine.sunproxy.net/file/... with base64-encoded parameters)
curl https://api.brin.sh/domain/angel-baby-rosie-the-originals.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
angel-baby-rosie-the-originals.hydr0.org currently scores 73/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.