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 2390495919.hydr0.org but presents itself entirely as MP3.cc, including a canonical tag pointing to https://mp3.cc/, all internal links pointing to mp3.cc, and all branding as MP3.cc. This is a domain-spoofing/proxy redirect where traffic arriving at the hydr0.org subdomain is transparently served mp3.cc content, likely to intercept or manipulate user traffic without their awareness. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/"> and all href/src attributes throughout)
brand impersonation
The site at 2390495919.hydr0.org fully impersonates MP3.cc: identical title ('Most popular songs | Download mp3 free, listen music online - MP3.cc'), logo, branding, OG tags (og:site_name=MP3.cc, og:url=https://mp3.cc/), and footer copyright '© 2017 – 2026 MP3.cc'. The subdomain numeric prefix (2390495919) on hydr0.org is a strong indicator of a bulk-generated proxy or scraper domain serving cloned content under a different domain to attract users. (location: page.html:5,11,14 - title, og:site_name, og:url; page.html:1184 - footer copyright)
malicious redirect
All audio file play links resolve to https://fine.sunproxy.net/file/... with long base64-encoded path tokens. The 'sunproxy.net' domain acts as a third-party proxy/CDN for serving MP3 files, routing all media traffic through an unaffiliated intermediary. The base64 path tokens (12 flagged by Tier 2 scan) encode opaque parameters that cannot be verified without decoding, and could contain tracking, redirect, or payload delivery logic. This explains the 12 'suspicious base64 blobs' flagged in the pre-scan. (location: page.html:228,247,266 etc. - data-url attributes on playlist-play anchors pointing to fine.sunproxy.net)
social engineering
The site offers free MP3 downloads of copyrighted music (Taylor Swift, Drake, Post Malone, etc.), which constitutes copyright infringement. This is a social engineering lure — the promise of free, illegal music downloads is used to attract users to a domain-spoofed proxy site, potentially exposing them to tracking, ad fraud, or malware delivery through the sunproxy.net media pipeline. (location: page.html:224 - playlist of popular copyrighted songs offered for free download; footer hydrofm@yandex.com contact)
curl https://api.brin.sh/domain/2390495919.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2390495919.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.