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 hosted at 2395806767.hydr0.org but all canonical tags, OG metadata, CSS, JS, and links point to mp3.cc. The page was served from a numeric subdomain of hydr0.org while impersonating the mp3.cc brand and infrastructure. This constitutes a redirect/mirror site pattern where users land on a different domain than the canonical content domain, which is a common technique in traffic hijacking and ad-fraud operations. (location: metadata.json:url=https://2395806767.hydr0.org; page.html:9 (canonical href=https://mp3.cc/))
brand impersonation
The site at 2395806767.hydr0.org fully impersonates mp3.cc — including its title, logo, branding, canonical URL, OG tags, CSS/JS assets loaded from mp3.cc, and all navigation links pointing to mp3.cc. The domain hydr0.org is unrelated to mp3.cc. The contact email in the footer (hydrofm@yandex.com) uses a Yandex address not associated with mp3.cc's legitimate domain. This is a complete brand/site clone operating under a deceptive domain. (location: page.html:5 (title), page.html:9 (canonical), page.html:18-19 (assets from mp3.cc), page.html:1184 (footer copyright + hydrofm@yandex.com))
malicious redirect
All MP3 playback URLs route through fine.sunproxy.net, a third-party proxy domain unrelated to mp3.cc. These base64-encoded URLs (12 suspicious base64 blobs flagged by Tier 2) serve media files tagged with '(Hydr0.org)' in filenames, indicating this proxy intercepts and re-routes all media traffic through an operator-controlled intermediary. This enables traffic monitoring, ad injection, or payload delivery via the proxy. (location: page.html:228 (data-url=https://fine.sunproxy.net/file/NDgw...), all playlist items use fine.sunproxy.net URLs)
hidden content
The MP3 filenames served through the sunproxy CDN contain '(Hydr0.org)' branding embedded in the file paths, revealing the true operator identity is hydr0.org rather than mp3.cc. This is a subtle disclosure hidden within encoded URLs that would not be apparent to normal users browsing the visible page content. (location: page.html:228 (Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3), and all other playlist data-url attributes)
curl https://api.brin.sh/domain/2395806767.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2395806767.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.