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.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The scanned URL (https://2056676534.hydr0.org) presents itself as MP3.cc via canonical tag, OG tags, all internal links, and copyright notice, but the actual serving domain is a numeric subdomain of hydr0.org — a completely different domain. This is a redirect/cloaking pattern where traffic is funneled through a shadow domain to the MP3.cc brand identity, bypassing any blocklist entries on the shadow domain while appearing legitimate. (location: page.html:9 (canonical href), page.html:14 (og:url), metadata.json (url field vs. canonical))
brand impersonation
The page fully impersonates MP3.cc — using its logo, title, meta tags, canonical URL, all navigation links, footer copyright, and contact email (hydrofm@yandex.com) — while being served from a different domain (2056676534.hydr0.org). This constitutes complete brand impersonation of MP3.cc on a shadow infrastructure domain. (location: page.html:5,9,11,14,33-36,1184)
malicious redirect
All audio file play links resolve through 'fine.sunproxy.net', a third-party proxy domain not affiliated with MP3.cc. Audio streams are routed through this intermediary rather than served directly, enabling potential traffic interception, user tracking, or malware delivery via audio file downloads. MP3 filenames contain '(Hydr0.org)' branding confirming intentional association with the shadow domain operator. (location: page.html:228,247,266,285 (data-url attributes on playlist-play links))
social engineering
MP3 filenames embedded in the audio URLs contain the tag '(Hydr0.org)', associating downloaded files with the shadow domain operator. Users downloading files receive files branded with the shadow domain name rather than the legitimate MP3.cc brand, potentially building familiarity and trust with the malicious operator's domain. (location: page.html:228 (Hydr0.org in all .mp3 filenames within data-url attributes))
curl https://api.brin.sh/domain/2056676534.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2056676534.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.