context safety score
A score of 55/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is served from edx-feat-jess-ball.hydr0.org but all canonical links, assets (CSS, JS), and internal navigation point to mp3.cc. The subdomain acts as a mirror/proxy that transparently redirects content from mp3.cc, consistent with the 1 redirect noted in the pre-scan context. This domain spoofing pattern — using a keyword-stuffed subdomain on hydr0.org to serve another site's content — is a common technique for SEO abuse, traffic hijacking, and evading blocklists. (location: page.html:9 (canonical href), page.html:18-19 (CSS/JS src), metadata.json (url vs canonical))
brand impersonation
The site at edx-feat-jess-ball.hydr0.org fully replicates the MP3.cc brand, including its logo, site name, copyright notice ('© 2017 – 2026 MP3.cc'), navigation, and UI. The serving domain has no affiliation with mp3.cc and presents itself as the legitimate service to visitors and crawlers. (location: page.html:5 (title), page.html:595 (footer copyright), page.html:33-36 (logo))
malicious redirect
All audio file download/play URLs resolve through fine.sunproxy.net, a third-party proxy domain, rather than directly from mp3.cc or the hosting domain. The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged in pre-scan) obscure the actual file destinations and could be used to route traffic, track users, or serve malicious payloads instead of audio files. (location: page.html:228 (data-url attribute), page.html:247, page.html:266 — all playlist-play links use fine.sunproxy.net)
hidden content
The base64 strings embedded in every audio URL (e.g., 'YVlGMWFTTXN3M0VjVThHdEhvZHd2aEUvN0prK0gv...') are non-trivial encoded blobs. While they may be legitimately obfuscated file tokens, 12 were flagged as suspicious by the pre-scan heuristic. Their content is opaque and cannot be verified without decoding, making them a potential vector for hidden payloads or tracking parameters. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570 (data-url attributes throughout playlist))
social engineering
The page presents free MP3 downloads of copyrighted music (EDX, Jess Ball tracks) as a legitimate service. This is a common lure to attract users into clicking download links that route through third-party proxy infrastructure (fine.sunproxy.net), potentially exposing them to unwanted software, tracking, or malicious file delivery. (location: page.html:229 (download links), page-text.txt:135-136 (play/download calls to action))
curl https://api.brin.sh/domain/edx-feat-jess-ball.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
edx-feat-jess-ball.hydr0.org currently scores 55/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.