context safety score
A score of 51/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
5 deceptive links where visible host does not match destination host
brand impersonation
The page is served from dr-dre-deep-cover-instrumental.hydr0.org but fully impersonates MP3.cc: it uses the MP3.cc logo, title, canonical URL, og:site_name, og:url, and loads CSS/JS directly from mp3.cc. The site presents itself as MP3.cc to users while being hosted on a completely different domain (hydr0.org), constituting clear brand impersonation of the legitimate MP3.cc service. (location: page.html:5,9,11,14,18,19,33-36 — title, canonical, og tags, logo, stylesheet, script all reference mp3.cc)
malicious redirect
The scanned URL (dr-dre-deep-cover-instrumental.hydr0.org) triggered 1 redirect per pre-scan analysis. The canonical and OG metadata point to mp3.cc, indicating the domain may redirect users to or proxy content from mp3.cc, potentially intercepting traffic or serving modified content through a third-party domain not controlled by MP3.cc. (location: metadata context — brin-context.md:19; page.html:9,14 canonical/og:url pointing to mp3.cc)
malicious redirect
All 23 audio play links route through fine.sunproxy.net — a third-party proxy domain — using obfuscated base64-encoded path segments. Audio streams are proxied through an external service (fine.sunproxy.net) instead of being served directly, which could be used to track user requests, log IP addresses, or serve malicious payloads in place of audio files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 — all data-url attributes)
social engineering
The page presents copyright notice as '© 2017–2026 MP3.cc' with a Yandex-hosted contact email (hydrofm@yandex.com) rather than an official MP3.cc domain email, suggesting the page is operated by an unauthorized third party masquerading as the legitimate MP3.cc brand to build false trust with users. (location: page.html:671 — footer copyright block)
curl https://api.brin.sh/domain/dr-dre-deep-cover-instrumental.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-dre-deep-cover-instrumental.hydr0.org currently scores 51/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.