context safety score
A score of 63/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
brand impersonation
The page is served from the subdomain beto-quintanilla-feat-banda-yurirense.hydr0.org but presents itself entirely as MP3.cc, including the MP3.cc logo, canonical URL pointing to mp3.cc, og:site_name 'MP3.cc', og:url pointing to mp3.cc, and footer copyright '© 2017–2026 MP3.cc'. The actual serving domain (hydr0.org) is not disclosed to the user anywhere on the page, creating a deceptive brand impersonation of the legitimate MP3.cc service. (location: page.html:5-14, page.html:614)
malicious redirect
The canonical link tag and all internal navigation links redirect users to mp3.cc rather than the serving domain hydr0.org. The page was accessed at hydr0.org but silently presents mp3.cc branding and canonical URLs, indicating the hydr0.org domain is a shadow/mirror site that may redirect or proxy traffic without user awareness. The brin-context also confirms 1 redirect was detected. (location: page.html:9, page.html:14, page.html:33)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with either the serving domain (hydr0.org) or the impersonated brand (mp3.cc). Audio stream data-url attributes point to 'https://fine.sunproxy.net/file/...' with base64-encoded path parameters (12 suspicious base64 blobs flagged by Tier 2 scan). This constitutes off-domain resource loading through an opaque proxy that could intercept user activity or serve malicious payloads. (location: page.html:228, page.html:247, page.html:266, page.html:285, page.html:304, page.html:323, page.html:342, page.html:361, page.html:380, page.html:399, page.html:418, page.html:437, page.html:456, page.html:475, page.html:494, page.html:513, page.html:532, page.html:551, page.html:570, page.html:589)
hidden content
The page footer contact email 'hydrofm@yandex.com' uses a Yandex (Russian) email address rather than any address associated with the impersonated MP3.cc brand. This is an indicator of the shadow-site operator's identity embedded in the page, not visible as a threat to casual users but significant for attribution and deception analysis. (location: page.html:614)
curl https://api.brin.sh/domain/beto-quintanilla-feat-banda-yurirense.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
beto-quintanilla-feat-banda-yurirense.hydr0.org currently scores 63/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.