context safety score
A score of 60/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 served from dragonforce-x-brawl-stars.hydr0.org but the canonical URL, all internal links, assets (CSS/JS), and branding point entirely to mp3.cc. The subdomain hydr0.org acts as a redirect/proxy layer that delivers mp3.cc content under a different domain, constituting a deceptive redirect/cloaking arrangement. The pre-scan context also confirms 1 redirect was detected. (location: page.html:9 - canonical tag href='https://mp3.cc/t/1808681414-dragonforce-x-brawl-stars/'; page served from hydr0.org)
brand impersonation
The site at hydr0.org reproduces the full MP3.cc brand identity—logo, CSS, JS, navigation, footer copyright '© 2017–2026 MP3.cc', and contact email hydrofm@yandex.com—without being the legitimate mp3.cc domain. This constitutes impersonation or unauthorized mirroring of the MP3.cc brand and service. (location: page.html:5,614 - title and footer copyright; all assets loaded from mp3.cc)
malicious redirect
All MP3 audio file play links route through fine.sunproxy.net, a third-party proxy/CDN domain unrelated to either hydr0.org or mp3.cc. Audio traffic is redirected through this intermediary, which could facilitate traffic interception, tracking, or malware delivery via tainted media files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 - data-url attributes pointing to fine.sunproxy.net)
hidden content
The page contains 12 suspicious base64 blobs as flagged by pre-scan heuristics. These are present in the data-url attributes of playlist items and encode opaque file paths served via fine.sunproxy.net. While they decode to MP3 file path strings, the obfuscation prevents transparent inspection of actual file destinations. (location: page.html:228,247,266 et al. - base64-encoded strings in data-url attributes of playlist-play anchors)
curl https://api.brin.sh/domain/dragonforce-x-brawl-stars.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dragonforce-x-brawl-stars.hydr0.org currently scores 60/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.