context safety score
A score of 73/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The page is served from blink-182-and-sum-41.hydr0.org but contains a canonical URL pointing to mp3.cc (https://mp3.cc/t/1246748327-blink-182-and-sum-41/). The pre-scan context confirms 1 redirect was detected. This subdomain on hydr0.org appears to be a mirror/clone of mp3.cc content, with all internal links pointing back to mp3.cc, indicating the hydr0.org domain is being used to proxy or redirect users to the mp3.cc service without being the authoritative source. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/1246748327-blink-182-and-sum-41/">)
brand impersonation
The site at blink-182-and-sum-41.hydr0.org presents itself as MP3.cc (logo, title, branding, copyright notice '© 2017–2026 MP3.cc') but is served from a different domain (hydr0.org). All assets, links, and navigation are loaded from mp3.cc, while the serving domain is hydr0.org. This constitutes brand impersonation or an unauthorized mirror of MP3.cc. The contact email in the footer (hydrofm@yandex.com) and the Hydr0.org branding embedded in mp3 filenames (e.g., 'Hydr0.org' suffix in all audio filenames) suggest the operator is distinct from MP3.cc but presenting MP3.cc's UI. (location: page.html:5 (title), page.html:633 (footer copyright), audio filenames in data-url attributes)
hidden content
All 12 audio file download links use base64-encoded tokens within URLs served via the third-party proxy domain fine.sunproxy.net. The base64 blobs decode to binary/encrypted data rather than plain URLs, obscuring the actual media file locations. While consistent with a token-based proxy pattern, the opaque encoded paths prevent verification of the actual content being served and could be used to serve unexpected content. (location: page.html:228-622 - data-url attributes containing https://fine.sunproxy.net/file/<base64>/filename.mp3)
curl https://api.brin.sh/domain/blink-182-and-sum-41.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
blink-182-and-sum-41.hydr0.org currently scores 73/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.