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 2040962568.hydr0.org but all canonical URLs, links, CSS, JS, and OG metadata point to mp3.cc. The canonical tag explicitly redirects search engines and agents to https://mp3.cc/, while the serving domain is a numeric subdomain of hydr0.org. This subdomain acts as a proxy/mirror that impersonates the mp3.cc brand from a different, unaffiliated domain. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/">; metadata.json domain: 2040962568.hydr0.org)
brand impersonation
The site fully impersonates MP3.cc — including its title ('Most popular songs | Download mp3 free, listen music online - MP3.cc'), logo, OG site_name ('MP3.cc'), all navigation links, footer copyright ('© 2017 – 2026 MP3.cc'), and static assets (CSS/JS) — while being hosted on the unrelated domain 2040962568.hydr0.org. This is a complete brand clone operating under a different domain. (location: page.html:5,11,18,19,33-36,1184; metadata.json domain field)
malicious redirect
All MP3 audio files are served through fine.sunproxy.net, a third-party proxy domain, rather than from mp3.cc or hydr0.org directly. The data-url attributes in playlist play links route audio through https://fine.sunproxy.net/file/[base64-encoded-path], meaning all media traffic is proxied through an unrelated third-party server that could intercept, log, or manipulate requests. (location: page.html:228,247,266,285,304 (and all subsequent playlist-play data-url attributes) — e.g. data-url="https://fine.sunproxy.net/file/NDgw...")
hidden content
The tier-2 scan flagged 12 suspicious base64 blobs. These correspond to the base64-encoded path segments in fine.sunproxy.net audio URLs (e.g. NDgwdkFuTUxJZ0tHbEJUVFE0QUZzNUtmT3Q5UlZlNlAveTNlSGJkYkhO...). While these appear to be encoded file paths rather than injected payloads, they do obfuscate the actual file locations and server-side routing logic, which is consistent with evasion of content filtering. (location: page.html:228,247,266,285,304 etc. — base64 path segments in fine.sunproxy.net URLs)
curl https://api.brin.sh/domain/2040962568.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2040962568.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.