context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
3 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on annalisa.hydr0.org but all canonical URLs, assets (CSS, JS), and links point to mp3.cc. The subdomain acts as a redirect/mirror for mp3.cc content, with the canonical tag explicitly redirecting crawlers and agents to https://mp3.cc/t/3482500638-annalisa/. This domain-fronting pattern is used to circumvent blocklists while serving third-party content. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/3482500638-annalisa/">)
malicious redirect
All MP3 play URLs resolve through fine.sunproxy.net, a third-party proxy service not affiliated with mp3.cc or hydr0.org. Audio file requests are routed through this intermediary proxy, which could intercept traffic, track users, or serve malicious payloads. The proxy URLs contain long base64-encoded path segments that obscure the actual file destinations. (location: page.html:228 - data-url="https://fine.sunproxy.net/file/NDgwd...")
brand impersonation
The site annalisa.hydr0.org presents itself as MP3.cc — including the MP3.cc logo, branding, site name, copyright notice '© 2017–2026 MP3.cc', and all navigation/footer links pointing to mp3.cc. The hosting domain (hydr0.org) is completely different from the branded domain (mp3.cc), constituting brand impersonation of the MP3.cc service. Users and agents visiting annalisa.hydr0.org would believe they are on mp3.cc. (location: page.html:5,33-36,647,652)
hidden content
12 suspicious base64 blobs flagged by Tier 2 analysis are present in the MP3 download URLs routed through fine.sunproxy.net. These base64-encoded path segments in the proxy URLs are opaque and conceal the actual destination of audio file requests, preventing URL-level analysis of where data is being sent or fetched from. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes on playlist-play anchors)
social engineering
The site offers free MP3 downloads of copyrighted music (Italian artist Annalisa's catalog) under the guise of a legitimate music platform. The 'Download MP3' and '(download)' calls to action encourage users to download files served via an opaque third-party proxy (fine.sunproxy.net), potentially exposing users to malicious file downloads. (location: page.html:229,648 - download links and footer)
malicious redirect
Three deceptive links were flagged by Tier 2 analysis. One confirmed case: the sidebar link to looz.net (Online Radio) is an off-brand external link with target='_blank' that opens a third-party site in a new tab, diverging from the mp3.cc branding context. Other links point to mp3.cc from a hydr0.org domain, constituting deceptive cross-domain linking. (location: page.html:204 - <a href="https://looz.net/" class="z__important no-ajax" target="_blank">)
curl https://api.brin.sh/domain/annalisa.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
annalisa.hydr0.org currently scores 47/100 with a suspicious 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.