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 subdomain 2017287099.hydr0.org but fully impersonates MP3.cc, using MP3.cc's title, logo, canonical URL (https://mp3.cc/), Open Graph metadata, and all internal links pointing to mp3.cc. The actual serving domain is unrelated to mp3.cc, presenting a convincing clone of a third-party brand on an unaffiliated host. (location: page.html:5,9,11,14,33 — <title>, canonical, og:site_name, og:url, logo href all reference mp3.cc while served from 2017287099.hydr0.org)
malicious redirect
The site performs at least one redirect (Tier 1 scan: Redirects: 1) routing users from 2017287099.hydr0.org to the MP3.cc impersonation page. Users navigating to the numeric subdomain are silently redirected to what appears to be a legitimate music site, masking the true origin domain. (location: metadata.json / .brin-context.md — redirect count: 1; landing domain 2017287099.hydr0.org vs displayed mp3.cc identity)
malicious redirect
All audio file playback URLs route through a third-party proxy domain 'fine.sunproxy.net' rather than mp3.cc's own servers. MP3 files are delivered via opaque base64-encoded paths on this external proxy, which could intercept, redirect, or substitute file downloads without user awareness. This aligns with the 12 suspicious base64 blobs flagged in Tier 2. (location: page.html:228,247,266,285 (and all playlist-play data-url attributes) — https://fine.sunproxy.net/file/<base64>/<filename>.mp3)
hidden content
All audio download filenames in the data-url attributes contain the string '(Hydr0.org)' embedded in the MP3 filename (e.g., 'Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3'). This watermarks files served through the proxy with the operator's actual domain identity, hidden within file metadata that most users would not inspect, while the visible UI only shows mp3.cc branding. (location: page.html:228,247,266,285 — all data-url MP3 filenames contain (Hydr0.org) tag)
curl https://api.brin.sh/domain/2017287099.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2017287099.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.