context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The domain bailey-zimmerman.hydr0.org serves content that clones MP3.cc (a third-party music download site), using MP3.cc's branding, logo, CSS, JS, and canonical URLs throughout the page. The site presents itself as MP3.cc while operating under a completely different domain (hydr0.org), deceiving users about the true origin of the content. (location: page.html:5,9,11,14,18,19,33 - title, canonical, og:site_name, og:url, stylesheet, and script all reference mp3.cc)
malicious redirect
The page includes a canonical link tag pointing to https://mp3.cc/t/3226662514-bailey-zimmerman/ and all download links redirect users to mp3.cc, while audio playback is proxied through fine.sunproxy.net — a third-party proxy domain not affiliated with mp3.cc. Users clicking play are silently redirected through sunproxy.net infrastructure rather than the canonical site. (location: page.html:9 (canonical redirect), page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 (all data-url attributes pointing to fine.sunproxy.net))
malicious redirect
All MP3 audio files are served via https://fine.sunproxy.net/file/ with long base64-encoded path tokens (12 suspicious base64 blobs flagged in Tier 2). This third-party proxy intercepts all media requests, enabling traffic interception, tracking, or substitution of delivered content without user awareness. (location: page.html:228 - data-url="https://fine.sunproxy.net/file/NDgwdkFu..." and all subsequent playlist entries)
brand impersonation
One track listing embeds 'mp3xa.cc' as part of the artist name ('Bailey Zimmerman & Dermot Kennedy feat. YoungBoy Never Broke Again [mp3xa.cc]'), advertising a competing piracy site inside track metadata to lure users to another domain. (location: page.html:518 - artist span contains '[mp3xa.cc]' branding)
social engineering
The site operates on a subdomain (bailey-zimmerman.hydr0.org) that mimics a legitimate artist fan/download page and impersonates the established mp3.cc service to build false trust. The 'hydr0.org' branding is embedded in every MP3 filename (e.g., 'Bailey_Zimmerman_-_Where_It_Ends_(Hydr0.org).mp3'), watermarking pirated content with the piracy site's brand to drive traffic. (location: page.html:285 - filename contains (Hydr0.org), repeated across all 20 track entries)
hidden content
The page comment at line 714 leaks a backend performance/server fingerprint string '0.864254; 1 (0.00055599212646484). (US|).' which reveals server-side execution timing and geolocation data. While not directly malicious, this information disclosure can aid targeted attacks against the infrastructure. (location: page.html:714 - HTML comment: <!-- 0.864254; 1 (0.00055599212646484). (US|). -->)
curl https://api.brin.sh/domain/bailey-zimmerman.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bailey-zimmerman.hydr0.org currently scores 36/100 with a suspicious verdict and low 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.