context safety score
A score of 59/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 on 'arizona-zervas-feat-john-wolf.hydr0.org' but presents content cloned from 'mp3.cc', with a canonical tag pointing to 'https://mp3.cc/t/2658182773-arizona-zervas-feat-john-wolf/'. The subdomain 'hydr0.org' is unrelated to mp3.cc, indicating a redirect/mirror site that serves mp3.cc content under a different domain. The pre-scan context also noted 1 redirect. Audio file URLs route through 'fine.sunproxy.net', a third-party proxy domain not affiliated with mp3.cc. (location: page.html:9 (canonical tag), page.html:228,247,266,285,304,323,342 (data-url attributes))
brand impersonation
The site at 'hydr0.org' fully impersonates MP3.cc (mp3.cc), reproducing its logo, layout, branding, CSS/JS assets, and content. All visual elements, navigation, and page structure are identical to mp3.cc while operating from an entirely different domain. The footer retains the original copyright notice '© 2017 – 2026 MP3.cc' and contact email 'hydrofm@yandex.com', falsely attributing the site to the legitimate brand. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:33-36 (logo), page.html:367 (footer copyright))
malicious redirect
All audio playback URLs route through 'fine.sunproxy.net', a third-party proxy not operated by mp3.cc. Each audio file URL contains a long base64-encoded path segment (matching the 7 suspicious base64 blobs flagged in Tier 2 analysis). This proxy intercepts all media requests and could serve malicious payloads, track users, or redirect to exploit pages instead of or in addition to serving audio files. (location: page.html:228,247,266,285,304,323,342 (data-url attributes pointing to fine.sunproxy.net))
social engineering
The site mimics a legitimate free MP3 download service (MP3.cc) to lure users into clicking download and play links that route through unaffiliated third-party infrastructure (fine.sunproxy.net, hydr0.org). Users trusting the familiar MP3.cc brand may unknowingly interact with proxied or substituted content. The domain name 'arizona-zervas-feat-john-wolf.hydr0.org' is crafted to appear as a direct music search result, increasing the likelihood of user trust. (location: page.html:1-448 (overall page structure and domain))
curl https://api.brin.sh/domain/arizona-zervas-feat-john-wolf.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
arizona-zervas-feat-john-wolf.hydr0.org currently scores 59/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.