context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
3 deceptive links where visible host does not match destination host
malicious redirect
The domain dr-dre-live.hydr0.org is a subdomain designed to impersonate or redirect users to mp3.cc content. The canonical URL, all CSS/JS assets, og:tags, and internal links all point to mp3.cc (a third-party domain), while the actual serving domain is the suspicious hydr0.org subdomain. The page is effectively a mirror/proxy of mp3.cc hosted on an unrelated domain, redirecting users to mp3.cc infrastructure. One redirect was confirmed in Tier 2 scan. (location: page.html:9 (canonical href), page.html:18-19 (external assets), metadata.json (domain: dr-dre-live.hydr0.org))
brand impersonation
The site presents itself as MP3.cc (branding, logo, copyright '2017-2026 MP3.cc', all navigation links) while being served from the unrelated domain dr-dre-live.hydr0.org. This is a clear impersonation of the MP3.cc brand on a third-party domain, likely to siphon traffic or serve malicious content under the guise of a legitimate music service. (location: page.html:5 (title tag), page.html:652 (footer copyright), page.html:33 (logo link to mp3.cc))
malicious redirect
All 20 audio file playback URLs resolve through fine.sunproxy.net, a third-party proxy service, rather than mp3.cc or the hosting domain. The base64-encoded path parameters (12 suspicious base64 blobs flagged in Tier 2) in these URLs obfuscate the final destination of audio file requests, routing user traffic and potentially user data through an intermediary proxy. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 (data-url attributes on playlist-play links))
hidden content
The page title and URL use 'dr-dre-live' as a lure keyword while the canonical link redirects to a different URL path on mp3.cc. The 12 suspicious base64 blobs embedded in audio proxy URLs obfuscate actual file destinations and could conceal tracking or exfiltration parameters within the encoded strings passed to fine.sunproxy.net. (location: page.html:228 (data-url base64 parameter example: YVlGMWFTTXN3M0Vj...))
social engineering
The page mimics a legitimate music streaming/download service (MP3.cc) with familiar UX patterns (genre navigation, playlist, download buttons) to build user trust and encourage interaction with content served through a proxy chain (hydr0.org -> fine.sunproxy.net). The footer email hydrofm@yandex.com associates the site with a Yandex email rather than any official MP3.cc contact, suggesting the operator is masquerading as MP3.cc. (location: page.html:652 (footer: hydrofm@yandex.com), page.html:5 (title), page.html:204 (looz.net external link with class z__important))
curl https://api.brin.sh/domain/dr-dre-live.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-dre-live.hydr0.org currently scores 42/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.