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
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted at black-sun.hydr0.org but all canonical URLs, assets, links, and content point to mp3.cc (a third-party domain). The canonical tag explicitly redirects to https://mp3.cc/t/947059367-black-sun/, indicating the subdomain acts as a redirect/proxy/mirror layer over mp3.cc content without clear authorization or disclosure. The pre-scan context also confirmed 1 redirect was detected. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/947059367-black-sun/">)
brand impersonation
The page presents itself as MP3.cc (title, logo, branding, copyright '© 2017–2026 MP3.cc') while being served from the unrelated domain black-sun.hydr0.org. This constitutes brand impersonation — users and AI agents navigating to this subdomain would believe they are on the legitimate MP3.cc site. (location: page.html:5 - <title>Black Sun | Download mp3 free, listen music online - MP3.cc</title>; page.html:671 - footer copyright)
malicious redirect
All audio file download/play URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with the hosting domain black-sun.hydr0.org or the branded domain mp3.cc. Audio files pass through an intermediary proxy service, creating potential for traffic interception or substitution. (location: page.html:228 - data-url="https://fine.sunproxy.net/file/..." (all playlist items))
hidden content
The base64-encoded strings embedded in all audio file URLs (12 suspicious base64 blobs flagged by pre-scan) within data-url attributes of playlist items are opaque encoded payloads routed through fine.sunproxy.net. While individually they may be encoded file paths, the combination of 12 such blobs passed through an external proxy represents obfuscated routing logic that cannot be verified without decoding and resolving each URL. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes on playlist-play anchors)
curl https://api.brin.sh/domain/black-sun.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
black-sun.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.