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
malicious redirect
The page is hosted on a subdomain of hydr0.org (bob-sinclar-feat-queen-ifrica-vybrate-makedah.hydr0.org) but all canonical links, CSS, JS, and navigation point to mp3.cc. The page presents itself as mp3.cc content while being served from a different domain (hydr0.org), indicating a domain spoofing/redirect setup where traffic is captured on hydr0.org and content is mirrored from mp3.cc. (location: page.html:9 - canonical href, page.html line 1 - serving domain vs. canonical domain)
brand impersonation
The page fully impersonates mp3.cc — including its logo, branding, navigation, CSS/JS assets loaded directly from mp3.cc, and copyright notice '© 2017–2026 MP3.cc' — while being served from the unrelated domain hydr0.org. This is a complete brand clone of a third-party service. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:614 (footer copyright), metadata.json (domain: hydr0.org))
malicious redirect
All MP3 audio files are served through fine.sunproxy.net, a third-party proxy domain, rather than directly from mp3.cc or the hosting domain. The data-url attributes on play buttons all route through fine.sunproxy.net/file/ with base64-encoded path tokens. This intermediary proxy could intercept requests, track users, or serve malicious files. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589 (data-url attributes))
hidden content
The pre-scan context flagged 12 suspicious base64 blobs. These correspond to the base64-encoded tokens in the fine.sunproxy.net file URLs (e.g. NDgwdkFuTUxJZ0tH...). While these appear to be encoded file path tokens for the proxy, they are opaque and cannot be verified without decoding and resolving — consistent with a proxy obfuscation pattern. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 (data-url base64 segments in fine.sunproxy.net URLs))
curl https://api.brin.sh/domain/bob-sinclar-feat-queen-ifrica-vybrate-makedah.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bob-sinclar-feat-queen-ifrica-vybrate-makedah.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.