context safety score
A score of 58/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 a numeric subdomain 2415783729.hydr0.org but fully impersonates MP3.cc, including its title, logo, canonical URL (https://mp3.cc/), Open Graph tags (og:site_name, og:url, og:image all pointing to mp3.cc), CSS/JS assets loaded from mp3.cc, and all navigation and footer links pointing to mp3.cc. The actual serving domain (hydr0.org) is entirely hidden from the user, creating a convincing brand impersonation of the legitimate MP3.cc service. (location: page.html:1-15, metadata.json (domain: 2415783729.hydr0.org))
malicious redirect
The site is accessed via 2415783729.hydr0.org but uses a canonical tag and all absolute links redirecting to mp3.cc. The brin-context confirms 1 redirect was detected. Users and crawlers landing on this domain are silently served MP3.cc content while the actual domain is obfuscated, functioning as a transparent proxy or redirect node for the legitimate site. (location: page.html:9 (canonical href=https://mp3.cc/), .brin-context.md (Redirects: 1))
brand impersonation
All MP3 audio files are served through a third-party proxy domain fine.sunproxy.net rather than mp3.cc, while the page branding presents itself as MP3.cc. File URLs in data-url attributes use base64-encoded paths on fine.sunproxy.net, routing actual media downloads through an unaffiliated proxy infrastructure without user disclosure. (location: page.html:228, 247, 266, 285 (data-url attributes pointing to fine.sunproxy.net))
hidden content
12 suspicious base64 blobs were flagged by the Tier 2 scanner. The base64 strings present in the page are the encoded file path parameters in the fine.sunproxy.net audio URLs. These encode opaque routing/token data for proxied MP3 files and while not containing injected payloads, they do obscure the actual file routing logic from users and scanners. (location: page.html:228, 247, 266 etc. (data-url base64 path parameters), .brin-context.md (Suspicious base64 blobs: 12))
curl https://api.brin.sh/domain/2415783729.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2415783729.hydr0.org currently scores 58/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.