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 page is hosted at c418.hydr0.org but all canonical links, CSS, JS, and content links point to mp3.cc. The canonical URL is explicitly set to https://mp3.cc/t/3940602008-c418/, indicating a redirect/mirror site that funnels traffic from the hydr0.org domain to mp3.cc. The brin-context confirms 1 redirect was detected. (location: page.html:9 - <link rel='canonical' href='https://mp3.cc/t/3940602008-c418/'>)
brand impersonation
The site at c418.hydr0.org presents itself as MP3.cc, using the MP3.cc logo, branding, CSS, JavaScript, and all infrastructure from mp3.cc. The actual domain is hydr0.org, a different domain from mp3.cc, creating a brand impersonation scenario where users landing on hydr0.org see the MP3.cc brand. (location: page.html:5 - title tag 'C418 | Download mp3 free, listen music online - MP3.cc'; page.html:11 - og:site_name='MP3.cc')
malicious redirect
All audio file download/play requests are proxied through fine.sunproxy.net rather than served directly. This third-party proxy domain (sunproxy.net) intercepts all media requests, potentially for tracking, data harvesting, or serving malicious content in place of expected files. The base64-encoded URLs embedded in data-url attributes (12 suspicious base64 blobs flagged) route through this proxy. (location: page.html:228 - data-url='https://fine.sunproxy.net/file/NDgwd...' (and all subsequent playlist entries))
hidden content
Multiple artist entries use Cyrillic homoglyph characters (С418 using Cyrillic 'С' instead of Latin 'C') that are visually identical to the legitimate artist name C418. These homoglyph substitutions could be used to create separate artist namespaces or mislead users/search engines about content provenance. (location: page.html:252 - 'С418 - Daniel Rosenfeld'; page.html:271 - 'С418'; page.html:461 - 'С418'; page.html:537 - 'С418')
curl https://api.brin.sh/domain/c418.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
c418.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.