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.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted at astrix-ft.hydr0.org but all canonical URLs, links, assets (CSS, JS), and branding point exclusively to mp3.cc. The subdomain astrix-ft.hydr0.org serves content that impersonates mp3.cc, redirecting users who land on the typosquatting/alternate domain into the mp3.cc ecosystem without disclosure. The canonical tag (line 9 of page.html) forces search engines to attribute the content to mp3.cc while the actual serving domain is different. (location: page.html:9, metadata.json:1)
brand impersonation
The site at astrix-ft.hydr0.org fully replicates the MP3.cc brand: identical title tag ('MP3.cc'), logo, CSS/JS assets from mp3.cc CDN, og:site_name set to 'MP3.cc', and footer copyright '2017-2026 MP3.cc'. The serving domain (hydr0.org subdomain) is not mp3.cc, suggesting an unauthorized mirror or cloned site impersonating the MP3.cc brand. (location: page.html:5,11,18,19,671)
malicious redirect
All audio file playback URLs route through the third-party proxy domain fine.sunproxy.net with long base64-encoded path tokens. This intermediary proxy (not mp3.cc or hydr0.org) handles all media delivery and could perform traffic interception, tracking, or serve modified content. The 12 suspicious base64 blobs flagged in Tier 2 correspond to these proxy URL tokens. (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,646)
social engineering
The page presents itself as a free MP3 download/streaming service. The contact email in the footer (hydrofm@yandex.com) uses a Russian email provider (Yandex), inconsistent with an English-language Western music service branding as MP3.cc. This combination of a non-authoritative domain, cloned branding, and foreign contact details is characteristic of piracy/scraper sites that may engage in deceptive practices toward users. (location: page.html:671)
curl https://api.brin.sh/domain/astrix-ft.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
astrix-ft.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.