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
brand impersonation
The page is served from subdomain 2450315010.hydr0.org but fully impersonates MP3.cc by copying its title, meta tags (og:site_name, og:url, canonical), logo, CSS/JS assets, and all internal links. The actual domain (hydr0.org) is completely hidden from the user, who sees only the MP3.cc brand. This constitutes brand impersonation of an established music download service. (location: page.html:5,9,11,14,18,19,33 — <title>, canonical, og:url, og:site_name all reference mp3.cc while the serving domain is 2450315010.hydr0.org)
malicious redirect
The site is a mirror/proxy of mp3.cc served from a numerically-named subdomain (2450315010.hydr0.org). The brin-context confirms 1 redirect occurred. All content assets (CSS, JS, images) and canonical URLs point back to mp3.cc, indicating this domain intercepts traffic that should go to the legitimate site, potentially to insert ads, track users, or serve modified content. (location: metadata.json — url: https://2450315010.hydr0.org; page.html:9 — canonical href='https://mp3.cc/')
malicious redirect
All MP3 audio files are served through a third-party proxy domain 'fine.sunproxy.net' rather than the canonical mp3.cc infrastructure. The file paths contain long base64-encoded tokens (12 suspicious base64 blobs flagged by Tier 2). Users clicking play are silently redirected to fine.sunproxy.net for file delivery, which could be used to track users, serve modified files, or intercept download activity. (location: page.html:228,247,266 — data-url attributes pointing to https://fine.sunproxy.net/file/NDgw...)
hidden content
The footer contains a contact email using a Yandex address (hydrofm@yandex.com) rather than any official MP3.cc contact. The copyright claim '© 2017–2026 MP3.cc' paired with a Yandex email on a non-mp3.cc domain suggests the operator is masquerading as the official service while concealing their true identity behind a Russian free email provider. (location: page.html:1184 — <div id='foo-copyright'>© 2017 – 2026 MP3.cc<br />hydrofm@yandex.com</div>)
curl https://api.brin.sh/domain/2450315010.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2450315010.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.