context safety score
A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is served from destructo.hydr0.org but all canonical URLs, resources (CSS, JS), links, and branding point to mp3.cc. The subdomain hydr0.org is acting as a mirror/proxy of mp3.cc content, with a redirect (1 redirect noted in pre-scan). This constitutes a domain impersonation redirect where users landing on hydr0.org are silently served mp3.cc content without being on the legitimate domain. (location: page.html:9 - canonical href='https://mp3.cc/t/1504481030-destructo/', metadata.json domain=destructo.hydr0.org)
brand impersonation
The site at destructo.hydr0.org clones the full MP3.cc brand identity including logo, site name 'MP3.cc', copyright notice '© 2017–2026 MP3.cc', and all navigation/content, without being the legitimate mp3.cc domain. This constitutes brand impersonation of MP3.cc by the hydr0.org operator. (location: page.html:5,35,652 - title and footer copyright reference MP3.cc while hosted on hydr0.org)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. Audio streams are proxied through this intermediary, which could intercept traffic, serve malicious files, or track users. The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged in pre-scan) are consistent with obfuscated file routing through a proxy. (location: page.html:228,247,266 etc. - data-url attributes pointing to https://fine.sunproxy.net/file/<base64>)
hidden content
The page includes 12 base64-encoded blobs embedded in data-url attributes for audio playback links. While these decode to proxied MP3 file paths, the obfuscated routing through fine.sunproxy.net conceals the true destination of audio requests and the identity of the file server. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 etc. - data-url='https://fine.sunproxy.net/file/<base64_blob>')
social engineering
The page presents itself as a legitimate free MP3 download service (MP3.cc) while operating from a different domain (hydr0.org). Users are deceived into believing they are on the official MP3.cc site. The contact email 'hydrofm@yandex.com' in the footer is associated with hydr0.org, not MP3.cc, further obscuring the true operator identity. (location: page.html:652 - footer contains 'hydrofm@yandex.com' alongside '© 2017–2026 MP3.cc' branding)
curl https://api.brin.sh/domain/destructo.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
destructo.hydr0.org currently scores 58/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.