context safety score
A score of 37/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 page is served from a subdomain (dragon-s-newik-the-secret-radio-edit.hydr0.org) that fully impersonates MP3.cc, including cloned logo, navigation, CSS/JS assets loaded directly from mp3.cc, canonical tag pointing to mp3.cc, and Open Graph metadata identifying the site as MP3.cc. The actual domain is hydr0.org, not mp3.cc. (location: page.html:5-14, header and meta tags)
malicious redirect
The canonical link tag explicitly redirects search engines and crawlers to https://mp3.cc/t/1495271348-dragon-s-newik-the-secret-radio-edit/, while the actual serving domain is hydr0.org. This is a deliberate SEO cloaking technique to mask the true domain and divert link authority or user traffic. (location: page.html:9)
phishing
The site clones the full MP3.cc interface (logo, styles, scripts, footer copyright '© 2017–2026 MP3.cc') on a different domain (hydr0.org), presenting itself as the legitimate MP3.cc service to deceive users into trusting the site and downloading files from third-party proxy URLs (fine.sunproxy.net) rather than the real MP3.cc infrastructure. (location: page.html:538, all asset URLs referencing mp3.cc)
malicious redirect
All audio file download and play URLs resolve through fine.sunproxy.net, a third-party proxy service, rather than through mp3.cc directly. The data-url values in playlist entries are Base64-encoded strings passed to fine.sunproxy.net/file/, obfuscating the final download destination and routing user traffic and file requests through an unvetted intermediary. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513 (all data-url attributes))
obfuscated code
12 suspicious Base64 blobs are present as data-url attribute values on playlist play links. Each blob encodes an opaque token passed to fine.sunproxy.net, obscuring the true destination URLs of media files. This is consistent with obfuscated redirect chaining to hide the actual file source or track user activity. (location: page.html: all playlist-play anchor data-url attributes (lines 228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513))
social engineering
The page title and URL slug ('dragon-s-newik-the-secret-radio-edit') are crafted to appear as a legitimate, specific music search result page, increasing user trust and encouraging file downloads through the proxied sunproxy.net infrastructure. (location: page.html:5, metadata.json URL field)
curl https://api.brin.sh/domain/dragon-s-newik-the-secret-radio-edit.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dragon-s-newik-the-secret-radio-edit.hydr0.org currently scores 37/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.