context safety score
A score of 62/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
3 deceptive links where visible host does not match destination host
brand impersonation
The page is served from azz.hydr0.org but presents itself entirely as MP3.cc, including the logo, title tag ('Azz | Download mp3 free, listen music online - MP3.cc'), canonical URL pointing to mp3.cc, og:site_name set to 'MP3.cc', and footer copyright '© 2017–2026 MP3.cc'. The actual serving domain (azz.hydr0.org) is a lookalike/mirror that impersonates the legitimate MP3.cc brand without any disclosure. (location: page.html:5,9,11,14,671)
malicious redirect
The canonical link tag redirects to https://mp3.cc/t/3062759271-azz/ and all navigation links point to mp3.cc, while the page is actually hosted on azz.hydr0.org. This domain-level redirect/mirror pattern (noted as 1 redirect in pre-scan) means users and bots fetching azz.hydr0.org are transparently served a clone of mp3.cc, potentially for SEO manipulation, traffic hijacking, or to serve modified content to specific user-agents. (location: page.html:9 (canonical), metadata.json (redirects:1))
hidden content
The 12 suspicious base64 blobs flagged in Tier 2 are all present in the data-url attributes of playlist play buttons (e.g., data-url='https://fine.sunproxy.net/file/NDgwdkFu...'). Each blob is a base64-encoded string passed to a third-party proxy domain (fine.sunproxy.net) to resolve the actual MP3 file URL. While consistent with a streaming proxy pattern, the obfuscated URLs conceal the true file origin and bypass direct linking detection, qualifying as hidden/obfuscated content routing. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627)
malicious redirect
All MP3 audio files are proxied through fine.sunproxy.net using opaque base64-encoded path tokens rather than direct URLs. This third-party proxy intermediary could be used to track user requests, swap file content, or redirect to malicious payloads. The 'sunproxy.net' domain is not affiliated with the displayed MP3.cc brand. (location: page.html:228 (data-url attribute, representative of all 22 playlist items))
curl https://api.brin.sh/domain/azz.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
azz.hydr0.org currently scores 62/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.