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
malicious redirect
The page is hosted on 233687187.hydr0.org but presents itself entirely as MP3.cc, with canonical URL, og:url, all internal links, logo, and footer pointing to https://mp3.cc/. The actual serving domain is a numeric subdomain of hydr0.org — a separate, unrelated domain. All user interactions and navigation are silently redirected to mp3.cc assets and links, constituting a redirect/cloaking arrangement where the true serving origin is concealed. (location: page.html:9 (canonical), page.html:14 (og:url), page.html:33 (logo href), metadata.json (domain: 233687187.hydr0.org))
brand impersonation
The page fully impersonates the MP3.cc brand: title tag reads 'Most popular songs | Download mp3 free, listen music online - MP3.cc', og:site_name is 'MP3.cc', the logo links to mp3.cc, and all footer/navigation links reference mp3.cc. The actual domain serving the page is 233687187.hydr0.org, which has no affiliation with mp3.cc. This is a mirror/clone impersonating a third-party music service. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:33 (logo), page.html:1184 (footer copyright))
malicious redirect
All MP3 audio file download links route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. The data-url attributes on every play button point to https://fine.sunproxy.net/file/... with base64-encoded path parameters. This intermediary proxy intercepts all media requests, potentially logging user activity, substituting files, or serving malware. The 12 suspicious base64 blobs flagged in Tier 2 correspond to these encoded file path tokens. (location: page.html:228 (first data-url), page.html:247, page.html:266 (and all subsequent playlist items))
hidden content
A comment in Russian appears in the HTML source at line 1226: '<!-- !info - чтобы показать #fixplayer-notification нужно добавить .js__notify для #fixplayer-lcd -->' indicating the codebase or its authors are Russian-speaking, consistent with the hydrofm@yandex.com contact address (Yandex is a Russian email provider). While not directly malicious, this corroborates the non-Western origin of the site operating under a Western brand facade. (location: page.html:1226)
social engineering
The site uses the established MP3.cc brand identity (logo, title, genre navigation, playlist UI, copyright notice '© 2017–2026 MP3.cc') to build false trust and legitimacy for a site operating on a completely different domain (233687187.hydr0.org). Users and AI agents browsing or indexing this page would be deceived into believing they are interacting with the legitimate MP3.cc service when they are not. (location: page.html:5,9,11,14,33,1184; page-text.txt:1087)
curl https://api.brin.sh/domain/233687187.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
233687187.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.