context safety score
A score of 68/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 scanned URL (2-of-amerikaz-most-wanted-feat-snoop-dogg.hydr0.org) is a subdomain that impersonates MP3.cc content and redirects users to the legitimate mp3.cc site. The canonical tag and all links point to mp3.cc, indicating this subdomain acts as a traffic relay or typosquat proxy rather than being the authoritative content host. The brin-context confirms 1 redirect was detected. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/3658586169-2-of-amerikaz-most-wanted-feat-snoop-dogg/">)
brand impersonation
The subdomain hydr0.org hosts a full replica of MP3.cc's interface, including the MP3.cc logo, branding, stylesheet, JavaScript, and layout loaded from mp3.cc CDN assets. The site presents itself as MP3.cc to users while operating under a different domain (hydr0.org), constituting brand impersonation of the MP3.cc service. (location: page.html:5,18,19,33 - title tag, stylesheet/script src, and logo link all reference mp3.cc)
malicious redirect
All audio file playback URLs resolve through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. Audio streams are routed through this intermediary, which could be used for traffic interception, data collection, or serving malicious file payloads. The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged by Tier 2) obfuscate the actual file routing logic. (location: page.html:228,247,266 (and all playlist data-url attributes) - data-url="https://fine.sunproxy.net/file/NDgw...")
hidden content
The MP3 filenames embedded in the sunproxy.net URLs contain base64-encoded path segments (e.g. NDgwdkFuTUxJZ0tHbEJUVFE0QUZzeU50Smt3...) that decode to opaque routing tokens. These 12 base64 blobs obscure the true file source and routing destination, preventing users and agents from verifying where audio files actually originate or where requests are sent. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608 - all data-url attributes on playlist-play anchors)
curl https://api.brin.sh/domain/2-of-amerikaz-most-wanted-feat-snoop-dogg.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2-of-amerikaz-most-wanted-feat-snoop-dogg.hydr0.org currently scores 68/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.