context safety score
A score of 56/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 hosted at azzecca.hydr0.org but all content, assets, canonical URLs, and links point to mp3.cc — the subdomain acts as a redirect/proxy front for mp3.cc content. The canonical tag explicitly redirects crawlers and agents to https://mp3.cc/t/2802765590-azzecca/. This subdomain-based front is a common technique to obscure the true destination and evade domain-level blocklists. (location: page.html:9 — <link rel='canonical' href='https://mp3.cc/t/2802765590-azzecca/'>)
malicious redirect
All MP3 audio file streaming URLs route through fine.sunproxy.net, a third-party proxy/CDN domain not affiliated with mp3.cc or hydr0.org. Audio play links use data-url attributes pointing to fine.sunproxy.net/file/ with long base64-encoded path tokens. This proxy layer obscures the true file origin and could be used to serve malicious payloads or track user interactions. (location: page.html:228 — data-url='https://fine.sunproxy.net/file/NDgwd...')
brand impersonation
The site at azzecca.hydr0.org fully impersonates MP3.cc — using its logo, stylesheet, JavaScript, branding, site name, and all navigation links. The page title reads 'Azzecca | Download mp3 free, listen music online - MP3.cc' and Open Graph tags claim og:site_name='MP3.cc'. A user or agent visiting azzecca.hydr0.org would have no indication they are not on mp3.cc, constituting brand impersonation of MP3.cc by the hydr0.org operator. (location: page.html:5,11 — <title> and og:site_name)
hidden content
The page contains 12 suspicious base64 blobs embedded in the data-url attributes of playlist play links. These are encoded file path tokens passed to fine.sunproxy.net. While they may be legitimate file tokens, their use of opaque base64 encoding inside data attributes obscures the actual resource being fetched and prevents static analysis of the target URLs. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 — data-url base64 path tokens in fine.sunproxy.net URLs)
curl https://api.brin.sh/domain/azzecca.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
azzecca.hydr0.org currently scores 56/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.