context safety score
A score of 65/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
brand impersonation
The page is served from black-coast-m-maggie.hydr0.org but fully renders as MP3.cc, including the MP3.cc logo, site name, OG tags (og:site_name='MP3.cc'), canonical link pointing to mp3.cc, and copyright footer '© 2017–2026 MP3.cc'. Users and AI agents browsing this subdomain may believe they are on the legitimate MP3.cc domain. The operator contact (hydrofm@yandex.com) and MP3 filenames containing '(Hydr0.org)' suggest hydr0.org operates mp3.cc, making this a self-operated mirror rather than a third-party clone, but the subdomain still presents a deceptive brand identity inconsistent with the serving domain. (location: page.html:5-14, page.html:633 — title tag, og:site_name, canonical href, footer copyright)
malicious redirect
The pre-scan context records 1 redirect. The page's canonical tag points to https://mp3.cc/t/1255852055-black-coast-m-maggie/ while the actual serving domain is black-coast-m-maggie.hydr0.org. This indicates the subdomain acts as a gateway or mirror that may redirect users to mp3.cc or serve content inline, creating a domain-mismatch redirect chain that can obscure the true origin of content and tracking. (location: .brin-context.md: Redirects=1; page.html:9 — canonical href)
social engineering
The site offers free downloads of copyrighted music tracks (MP3 files), luring users with promises of free content ('Download mp3 free, listen music online'). Audio files are routed through a third-party proxy (fine.sunproxy.net) using obfuscated base64-encoded path tokens, obscuring the true file source from users. This pattern is consistent with piracy sites that socially engineer users into downloading content of uncertain provenance through proxy intermediaries. (location: page.html:5 — title; page.html:228,247,266 — data-url attributes pointing to fine.sunproxy.net with base64 path tokens)
curl https://api.brin.sh/domain/black-coast-m-maggie.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
black-coast-m-maggie.hydr0.org currently scores 65/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.