context safety score
A score of 58/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 served from subdomain 2063304591.hydr0.org but all canonical URLs, links, assets (CSS/JS), og:url, and content point exclusively to mp3.cc. The subdomain acts as a transparent proxy/mirror of mp3.cc, routing user traffic through an intermediary domain (hydr0.org) not controlled by the legitimate brand owner. This is a classic cloaking/proxying arrangement that can intercept user sessions, inject content, or exfiltrate data without user awareness. (location: page.html:9 (canonical href), page.html:14 (og:url), metadata.json (domain: 2063304591.hydr0.org vs content domain mp3.cc))
brand impersonation
The site fully impersonates mp3.cc — replicating its title, logo, branding, layout, navigation, playlist content, footer copyright, and contact email (hydrofm@yandex.com) — while being served from the unrelated domain 2063304591.hydr0.org. Users and automated agents interacting with this URL would believe they are on the legitimate mp3.cc service. (location: page.html:5 (title), page.html:33-36 (logo), page.html:1184 (footer copyright hydrofm@yandex.com))
malicious redirect
All MP3 audio file playback URLs are routed through fine.sunproxy.net rather than mp3.cc directly. The sunproxy.net domain acts as an intermediary proxy for all media file requests. This third-party proxy could log user behavior, swap file content, or serve malware payloads in place of legitimate audio files. The base64-encoded path segments in these URLs obscure the actual file destinations (12 suspicious base64 blobs flagged by Tier 2 scan). (location: page.html:228 (data-url attributes on playlist-play links, e.g. https://fine.sunproxy.net/file/NDgwd...))
social engineering
The site presents itself as a free MP3 download service offering copyrighted commercial music (Taylor Swift, Drake, Post Malone, etc.) for free download. This is a social engineering lure — the promise of free copyrighted content encourages users to interact with the site, potentially exposing them to drive-by attacks, malicious file downloads, or data collection through the sunproxy.net intermediary. (location: page.html:224 (playlist with commercial tracks), page.html:1179 (Download MP3 footer link))
curl https://api.brin.sh/domain/2063304591.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2063304591.hydr0.org currently scores 58/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.