context safety score
A score of 52/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
brand impersonation
The page is served from subdomain 3810722621.hydr0.org but fully impersonates mp3.cc, including its title, logo, canonical URL (https://mp3.cc/), Open Graph metadata, all internal navigation links, and footer copyright. The actual serving domain is a numeric subdomain of hydr0.org, which is unrelated to mp3.cc. This constitutes brand impersonation of the mp3.cc service. (location: page.html:5,9,11,14,33 — <title>, canonical link, og:site_name, og:url, logo href all point to mp3.cc while served from 3810722621.hydr0.org)
malicious redirect
The page redirects users from 3810722621.hydr0.org to content that appears to belong to mp3.cc, with a canonical tag and all resource links pointing to mp3.cc. The Tier 1 context confirms 1 redirect was detected. This redirect pattern is used to serve a cloned or proxied version of a legitimate site from an unrelated domain, enabling traffic interception and potential manipulation. (location: metadata.json — redirect count: 1; page.html:9 — <link rel="canonical" href="https://mp3.cc/">)
malicious redirect
All MP3 audio file play links resolve to fine.sunproxy.net, a third-party proxy domain, rather than mp3.cc directly. Media requests are routed through this intermediary, which could intercept, log, or manipulate traffic including HTTP referrer headers and user behavior data. The URLs contain long base64-encoded path components consistent with obfuscated routing tokens. (location: page.html:228,247,266,285 (and all playlist-play data-url attributes) — https://fine.sunproxy.net/file/<base64>/..._(Hydr0.org).mp3)
hidden content
The page contains a comment in the HTML footer with a server timing/debug string: '<!-- 0.004669; 1 (0.00068306922912598). (US|). -->' This leaks server-side processing metadata and geolocation hint (US) and may indicate server fingerprinting or session tracking infrastructure embedded in responses. (location: page.html:1265 — <!-- 0.004669; 1 (0.00068306922912598). (US|). -->)
social engineering
The site presents itself as a free, legitimate MP3 download service using the trusted mp3.cc brand identity (logo, site name, navigation, copyright) while operating from an unrelated suspicious numeric subdomain (3810722621.hydr0.org). This deceives users into trusting the site as the genuine mp3.cc, potentially leading them to download files served through an unverified third-party proxy (fine.sunproxy.net) or exposing them to future credential harvesting or malware delivery. (location: page.html:5,9,33-36,1184 — title, canonical, logo, copyright all impersonate mp3.cc while domain is 3810722621.hydr0.org)
curl https://api.brin.sh/domain/3810722621.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
3810722621.hydr0.org currently scores 52/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.