context safety score
A score of 63/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 subdomain 2224109209.hydr0.org but all canonical URLs, links, assets, and branding point to mp3.cc. The canonical tag explicitly sets the URL as https://mp3.cc/ while the actual serving domain is a numeric subdomain of hydr0.org. This is a domain-cloaking / traffic-interception pattern where a shadow domain proxies or mirrors a legitimate site, potentially intercepting user traffic, injecting content, or serving modified pages without the user realizing they are not on the real mp3.cc domain. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/">; served from https://2224109209.hydr0.org)
brand impersonation
The page fully impersonates mp3.cc — including its logo, title, branding, og:site_name, og:url, canonical link, footer copyright notice, and all navigation links — while being served from the unrelated domain 2224109209.hydr0.org. The footer even displays '© 2017 – 2026 MP3.cc' with a contact email of hydrofm@yandex.com, combining the MP3.cc brand with what appears to be operator contact info on a different domain. This constitutes brand impersonation of the mp3.cc service. (location: page.html:5,9,11,14,1184 - title, canonical, og:site_name, og:url, footer copyright)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net rather than mp3.cc or any canonical CDN. The domain fine.sunproxy.net is an off-brand third-party proxy used to serve MP3 files. This third-party intermediary could intercept, modify, or replace audio content, inject malware in downloads, or track user behavior without disclosure. The file paths contain long base64-encoded tokens, consistent with signed/tokenized proxy URLs but also consistent with obfuscated redirect chains. (location: page.html:228,247,266 (and all playlist data-url attributes) - data-url="https://fine.sunproxy.net/file/...")
hidden content
The base64 strings embedded in all audio proxy URLs (fine.sunproxy.net/file/<base64>) are flagged as 12 suspicious base64 blobs by static analysis. While individually these appear to be signed file path tokens (a common CDN pattern), they are opaque to the user and could encode redirect targets, tracking parameters, or exfiltration endpoints that are not visible in the HTML. The true destinations are not disclosed. (location: page.html - all playlist-play data-url attributes containing base64-encoded path segments at fine.sunproxy.net)
curl https://api.brin.sh/domain/2224109209.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2224109209.hydr0.org currently scores 63/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.