context safety score
A score of 59/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The page is served from casti-duki-emilia.hydr0.org but fully impersonates MP3.cc, including its logo, CSS/JS assets loaded from mp3.cc, canonical URL pointing to mp3.cc, and Open Graph metadata claiming site_name 'MP3.cc'. The subdomain hydr0.org is unrelated to mp3.cc, creating a deceptive clone that appears to be the legitimate MP3.cc site. (location: page.html:5-14, metadata.json (domain: casti-duki-emilia.hydr0.org))
malicious redirect
The page includes a canonical link tag redirecting to https://mp3.cc/t/2928000822-casti-duki-emilia/ and the pre-scan context flagged 1 redirect. The serving domain (hydr0.org) does not match the canonical domain (mp3.cc), indicating traffic may be intercepted or harvested before redirect. The user-agent diff ratio of 0.47 suggests the content served differs significantly between user agents, a common cloaking/redirect technique. (location: page.html:9, .brin-context.md (Redirects: 1, User-agent diff ratio: 0.47))
social engineering
The MP3 file download URL uses a proxy service at fine.sunproxy.net with a long obfuscated path containing base64-like encoded parameters (NDgwdkFuTUxJZ0tHbEJUVFE0QUZzeU50Smt3cnFoanUyVFdycUE0OVNpQlF4SWJHaGxHWSszNVBoOC9yNGtIV295dmxJaXFxYzVmajBoZzJRM3c0WnFTR2Rpb3huSjBjci92OTBrUXh5UEE9). This proxy pattern can be used to track user clicks, harvest IP/user-agent data, or serve malware instead of the expected MP3 file. (location: page.html:228)
hidden content
A suspicious base64 blob was flagged by the pre-scan heuristics (1 suspicious base64 blob detected). The MP3 download proxy URL at fine.sunproxy.net contains a long base64-encoded string that encodes an opaque payload. The decoded content is not visible to users and may conceal exfiltration parameters or tracking identifiers. (location: page.html:228, .brin-context.md (Suspicious base64 blobs: 1))
brand impersonation
All navigation links, genre links, DMCA, Feedback, and footer copyright point to mp3.cc, while the actual serving domain is hydr0.org. The footer contact email 'hydrofm@yandex.com' reveals the true operator uses a Yandex email associated with the hydr0.org domain, not mp3.cc, confirming this is an unauthorized clone masquerading as MP3.cc. (location: page.html:248-253)
curl https://api.brin.sh/domain/casti-duki-emilia.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
casti-duki-emilia.hydr0.org currently scores 59/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.