context safety score
A score of 52/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 subdomain 239669666.hydr0.org but fully impersonates MP3.cc, including its title, logo, canonical URL (https://mp3.cc/), Open Graph metadata, all internal links, and copyright notice. The domain hydr0.org is not mp3.cc; the zero substitution in 'hydr0' further obscures the true domain while mimicking the branding of a known music service. (location: page.html:5,9,11,14,33-36 and metadata.json domain field)
malicious redirect
The scanned URL is 239669666.hydr0.org, but the canonical tag, all navigation links, footer links, and Open Graph URL all point to https://mp3.cc/. The page presents itself as if it is mp3.cc while being hosted on a different domain, constituting a domain-spoofing redirect pattern. The pre-scan context also recorded 1 redirect signal. (location: page.html:9 (canonical), page.html:14 (og:url), page.html:1179-1181 (footer links))
malicious redirect
All audio file playback URLs route through a third-party proxy domain 'fine.sunproxy.net' rather than mp3.cc or the hosting domain. This intermediary proxy intercepts all media requests and could be used for traffic interception, data collection, or serving malicious payloads in place of audio files. (location: page.html:228,247,266,285,304 (data-url attributes on playlist-play anchors))
brand impersonation
MP3 filenames embedded in the sunproxy URLs contain '(Hydr0.org)' watermarks (e.g., 'Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3'), revealing that the actual content origin is hydr0.org, not the impersonated mp3.cc brand. This confirms deliberate brand spoofing infrastructure. (location: page.html:228,247,266,285 (data-url MP3 filename suffixes))
hidden content
The 'Other listen' sidebar section (page-text.txt line 1099-1101) contains a dense block of unsegmented keyword text spanning dozens of artist/track search terms crammed into a single run-on string. While not visually hidden via CSS, this pattern is consistent with SEO keyword stuffing used to manipulate search indexing and lure users to the fraudulent domain. (location: page.html:1200-1202, page-text.txt:1099-1101)
curl https://api.brin.sh/domain/239669666.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
239669666.hydr0.org currently scores 52/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.