context safety score
A score of 69/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 domain 29-33hz-unhealthy-zoglin.hydr0.org serves content that impersonates mp3.cc: the canonical URL, all asset URLs (CSS, JS, fonts), all navigation links, og:url, og:site_name, and footer copyright all point to mp3.cc. The scanned domain acts as a traffic capture/redirect layer funneling users to or through mp3.cc, while the actual audio files are proxied through fine.sunproxy.net — an off-domain proxy service with no clear affiliation to mp3.cc. (location: page.html:9 (canonical), page.html:18-19 (assets), page.html:291 (footer), metadata.json (domain))
brand impersonation
The page fully impersonates MP3.cc: it uses the MP3.cc logo SVG, title tag references MP3.cc, og:site_name is 'MP3.cc', all links point to mp3.cc, and the footer copyright reads '© 2017 – 2026 MP3.cc'. However, the page is served from the unrelated domain 29-33hz-unhealthy-zoglin.hydr0.org, not from mp3.cc. This is a cloned/mirrored site misrepresenting its origin. (location: page.html:5,11,33,291; metadata.json:domain)
malicious redirect
All three audio play links use data-url attributes pointing to fine.sunproxy.net, an off-domain proxy/CDN not affiliated with the displayed brand (mp3.cc). Audio content is silently proxied through this third-party service, which intercepts media requests. The base64-encoded path tokens in these URLs are opaque encrypted blobs that obscure the actual file origin. (location: page.html:228,247,266)
hidden content
Three base64-encoded opaque tokens are embedded as data-url attributes in audio play links. While they decode to binary/encrypted data (consistent with signed CDN tokens), they are not human-readable and obscure the true destination of media requests routed through fine.sunproxy.net. This matches the 'suspicious base64 blobs: 3' signal flagged in the pre-scan context. (location: page.html:228,247,266 (data-url attributes))
curl https://api.brin.sh/domain/29-33hz-unhealthy-zoglin.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
29-33hz-unhealthy-zoglin.hydr0.org currently scores 69/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.