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 2410921001.hydr0.org but presents itself entirely as MP3.cc, including canonical URL, og:url, all internal links, logo, and footer copyright. The canonical tag (line 9) points to https://mp3.cc/ while the actual serving domain is a numeric subdomain of hydr0.org. This is a redirect/cloaking setup where the hydr0.org subdomain silently proxies or mirrors mp3.cc content, exposing users to a domain they did not navigate to. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/">; metadata.json domain: 2410921001.hydr0.org)
brand impersonation
The site fully impersonates MP3.cc — using its logo, branding, title ('Most popular songs | Download mp3 free, listen music online - MP3.cc'), Open Graph metadata (og:site_name='MP3.cc', og:url='https://mp3.cc/'), all links pointing to mp3.cc, and footer copyright '© 2017 – 2026 MP3.cc'. The actual serving domain is 2410921001.hydr0.org, not mp3.cc. This constitutes brand impersonation of the legitimate MP3.cc service. (location: page.html:5,11,14,1184 - title, og:site_name, og:url, footer copyright)
malicious redirect
All audio file streaming URLs route through fine.sunproxy.net, a third-party proxy domain unrelated to either mp3.cc or hydr0.org. Every play link uses data-url pointing to https://fine.sunproxy.net/file/... with base64-encoded path parameters (accounting for the 12 suspicious base64 blobs flagged in Tier 2). This intermediary proxy could log user interactions, serve malicious files, or redirect traffic. The encoded file paths obscure the actual destination. (location: page.html:228,247,266 (and all playlist-play data-url attributes) - https://fine.sunproxy.net/file/<base64>/<filename>)
hidden content
Each MP3 filename embedded in the sunproxy.net URLs contains '(Hydr0.org)' as a suffix (e.g., 'Maluma_-_Corazon_(Hydr0.org).mp3'), branding downloaded files with the operator's domain. This is embedded in base64-encoded URL paths and not visible to casual users, functioning as a covert attribution/tracking tag in delivered media files. (location: page.html:228 - data-url filenames ending in _(Hydr0.org).mp3 across all playlist entries)
curl https://api.brin.sh/domain/2410921001.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2410921001.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.