context safety score
A score of 72/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 (destiny-s-child-cater-2.hydr0.org) redirects to content hosted under mp3.cc branding. The canonical link, OG tags, CSS/JS, and all navigation point to mp3.cc, while the serving domain is a separate hydr0.org subdomain. This domain substitution pattern — serving mp3.cc content from a third-party subdomain — is consistent with a cloaking or redirect abuse setup used to evade blocklists or serve different content to crawlers vs. users. (location: page.html:9 (canonical), metadata.json (domain: destiny-s-child-cater-2.hydr0.org vs mp3.cc content))
brand impersonation
The page fully impersonates mp3.cc — including its logo, site name, CSS, JS, footer copyright, and all internal links — while being served from the unrelated domain destiny-s-child-cater-2.hydr0.org. Users and automated agents would believe they are on mp3.cc when they are not. (location: page.html:5 (title), page.html:9 (canonical href), page.html:18-19 (mp3.cc assets), page.html:671 (footer copyright MP3.cc))
malicious redirect
All audio stream URLs point to fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. Audio files are routed through an opaque proxy layer with base64-encoded path parameters, obscuring the true file origin and enabling potential content substitution or tracking. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 (data-url attributes pointing to fine.sunproxy.net))
hidden content
The MP3 filenames embedded in the sunproxy.net URLs contain '(Hydr0.org)' watermarks in what appear to be base64-encoded path segments. The 12 suspicious base64 blobs flagged in pre-scan correspond to these obfuscated file path tokens in each audio URL. While the blobs appear to encode file routing parameters rather than injected commands, the encoding obscures true file paths from inspection. (location: page.html:228 (data-url base64 path: YVlGMWFT...), repeated across all 20+ playlist entries)
curl https://api.brin.sh/domain/destiny-s-child-cater-2.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
destiny-s-child-cater-2.hydr0.org currently scores 72/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.