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 scanned URL azu-feat-seamo.hydr0.org redirects to mp3.cc (canonical URL set to https://mp3.cc/t/3215096112-azu-feat-seamo/). The subdomain hydr0.org acts as a redirect/proxy front for mp3.cc, a known MP3 piracy site. One redirect was confirmed in Tier 2 signals. (location: <link rel="canonical" href="https://mp3.cc/t/3215096112-azu-feat-seamo/"> and metadata redirect count=1)
brand impersonation
The page at azu-feat-seamo.hydr0.org presents itself as MP3.cc — using the MP3.cc logo, branding, CSS, JS, and copyright notice — while being served from a different domain (hydr0.org). This impersonates the MP3.cc brand to lend legitimacy to a piracy mirror/proxy site. (location: <title>Azu Feat Seamo | Download mp3 free, listen music online - MP3.cc</title>, header logo, footer copyright '© 2017 – 2026 MP3.cc')
malicious redirect
All MP3 audio file play links resolve through fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc or hydr0.org. Audio URLs contain long base64-encoded path segments routed through this proxy, representing a deceptive link pattern (1 deceptive link flagged in Tier 2). Users clicking play are redirected through an opaque proxy which could serve malicious files or track users. (location: data-url attributes on playlist-play anchors, e.g. https://fine.sunproxy.net/file/NDgwd... (lines 228, 247, 266, etc.))
hidden content
12 suspicious base64 blobs were flagged in Tier 2 analysis. Inspection confirms these are the base64-encoded path segments embedded in all fine.sunproxy.net audio URLs (data-url attributes). While these decode to obfuscated file paths rather than injected payloads, the use of base64 encoding to obscure the actual destination file paths is a notable obfuscation technique consistent with piracy proxy infrastructure. (location: data-url attributes across playlist items, e.g. NDgwdkFuTUxJZ0tHbEJUVFE0QUZzOWVPY2dxOHhOTFV6... (lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, etc.))
curl https://api.brin.sh/domain/azu-feat-seamo.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
azu-feat-seamo.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.