context safety score
A score of 58/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 served from subdomain 2385992079.hydr0.org but all canonical tags, og:url, CSS, JS, images, and internal links point to mp3.cc. The actual serving domain (hydr0.org) is completely different from the branded domain (MP3.cc), indicating the hydr0.org subdomain acts as an unauthorized mirror or redirect proxy for the legitimate MP3.cc site. (location: page.html:9 - canonical href='https://mp3.cc/', og:url='https://mp3.cc/', while served from 2385992079.hydr0.org)
brand impersonation
The page fully replicates the MP3.cc brand identity — logo, title 'Most popular songs | Download mp3 free, listen music online - MP3.cc', site name meta tag, and all visual assets — while being hosted on the unrelated domain hydr0.org. This constitutes brand impersonation of the legitimate MP3.cc service. (location: page.html:5,11 - title and og:site_name both reference MP3.cc while served from hydr0.org)
malicious redirect
All MP3 audio file download/play URLs route through fine.sunproxy.net, a third-party proxy domain, rather than directly from mp3.cc. The base64-encoded path segments in these URLs (12 suspicious base64 blobs flagged in Tier 2) obfuscate the actual file routing and could facilitate traffic interception, analytics harvesting, or payload substitution. (location: page.html:228,247,266 - data-url and href attributes pointing to fine.sunproxy.net/file/<base64-encoded-path>)
hidden content
A section labeled 'Other listen' contains a dense block of unseparated song/artist keyword strings not presented in normal list format. This appears to be SEO keyword stuffing hidden within a low-visibility widget section, used to manipulate search engine indexing. (location: page-text.txt:1098-1101 - 'Other listen' block with run-on keyword string)
curl https://api.brin.sh/domain/2385992079.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2385992079.hydr0.org currently scores 58/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.