context safety score
A score of 55/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The scanned domain (dr-dre-snoop-dogg-busta-rhymes-anderson-paak.hydr0.org) is a subdomain that mirrors content from mp3.cc, with a canonical tag and all navigation/download links pointing to mp3.cc. The site functions as a redirect/proxy layer for the legitimate mp3.cc domain, with 1 redirect recorded in Tier 1 signals. Users arriving at the hydr0.org subdomain are silently funneled to mp3.cc infrastructure. (location: page.html:9 (canonical href), page.html:33 (logo link), all navigation and download links throughout)
brand impersonation
The site presents itself visually and functionally as MP3.cc (logo, branding, copyright '© 2017–2026 MP3.cc'), but is hosted on hydr0.org — a different domain entirely. This constitutes brand impersonation of the MP3.cc service, potentially used to intercept traffic, serve ads, or proxy requests without the knowledge of MP3.cc users. (location: page.html:5 (title tag), page.html:11 (og:site_name), page.html:386 (footer copyright), metadata.json (domain: hydr0.org))
malicious redirect
All audio file URLs use the third-party proxy domain 'fine.sunproxy.net' rather than mp3.cc or hydr0.org directly. This intermediary proxy intercepts all media requests and could log user IPs, inject malicious content, or serve modified files. The data-url values for all play buttons route through fine.sunproxy.net/file/ with base64-encoded path parameters. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361 (all data-url attributes on playlist-play anchors))
hidden content
The Tier 1 scan detected 8 suspicious base64 blobs. These correspond to the base64-encoded file path parameters in the fine.sunproxy.net media URLs. While each individually encodes a proxied file path, the pattern of routing all media through obfuscated base64 paths on a third-party proxy is consistent with evasion of direct URL inspection and could obscure the true destination of file downloads. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361 (data-url base64 segments in fine.sunproxy.net URLs))
social engineering
The page title and H2 tag use celebrity names (Dr. Dre, Snoop Dogg, Busta Rhymes, Anderson .Paak) combined with free MP3 download offers to attract users seeking copyrighted music. This pattern is commonly used to lure users into interacting with piracy proxy sites that may expose them to malware, unwanted redirects, or data collection. (location: page.html:5 (title), page.html:224 (h2), page-text.txt:131)
curl https://api.brin.sh/domain/dr-dre-snoop-dogg-busta-rhymes-anderson-paak.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-dre-snoop-dogg-busta-rhymes-anderson-paak.hydr0.org currently scores 55/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.