context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The page is served from a third-party subdomain (despina-vandi-mente-fuerte-teo-tzimas.hydr0.org) but fully mirrors the branding, layout, CSS, and JavaScript of mp3.cc — including its logo, navigation, and canonical URL pointing to mp3.cc. The hydr0.org domain is not mp3.cc, yet the page impersonates it completely, including the title tag and OG metadata claiming it is MP3.cc. (location: page.html:5-14, metadata.json (domain: despina-vandi-mente-fuerte-teo-tzimas.hydr0.org))
malicious redirect
The canonical link tag and all internal navigation links redirect users from the serving domain (hydr0.org) to mp3.cc. The pre-scan context notes 1 redirect was detected. The site is a mirror/proxy that funnels users to mp3.cc while serving content from an unrelated domain, a common technique for traffic hijacking or affiliate fraud. (location: page.html:9 (rel=canonical href=https://mp3.cc/...), .brin-context.md (Redirects: 1))
brand impersonation
All static assets (CSS, JS, fonts, images) are loaded directly from mp3.cc, and the page claims copyright '2017-2026 MP3.cc' and displays the mp3.cc contact email (hydrofm@yandex.com), presenting itself as the legitimate MP3.cc service while operating under a completely different domain. (location: page.html:18-19, page.html:386)
hidden content
The MP3 play links use data-url attributes pointing to fine.sunproxy.net with long base64-encoded path components. The pre-scan flagged 8 suspicious base64 blobs. These encoded strings in the audio file URLs obfuscate the actual download/streaming endpoint, routing media through an intermediary proxy (sunproxy.net) in a non-transparent way. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361 (data-url attributes with base64 paths to fine.sunproxy.net))
malicious redirect
All audio content is proxied through fine.sunproxy.net with opaque base64-encoded file identifiers rather than being served directly. This third-party proxy intercepts all media requests, enabling potential traffic interception, user tracking, or malware delivery via the audio endpoint. (location: page.html:228 (data-url=https://fine.sunproxy.net/file/YVlGM...), and all playlist items)
curl https://api.brin.sh/domain/despina-vandi-mente-fuerte-teo-tzimas.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
despina-vandi-mente-fuerte-teo-tzimas.hydr0.org currently scores 49/100 with a suspicious 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.