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
malicious redirect
The page is served from subdomain 2251176648.hydr0.org but all canonical links, CSS, JS, og:url, og:image, and internal navigation links point to mp3.cc. The actual URL serving the content is a numeric-subdomain on a different registrable domain (hydr0.org), while all branding and resources claim to be mp3.cc. This constitutes a redirect/proxy mirror that hides the true serving domain from users and crawlers. (location: page.html:9 (canonical href), page.html:14 (og:url), metadata.json domain field vs all href targets)
brand impersonation
The page fully impersonates the legitimate mp3.cc service: it uses the MP3.cc logo, title, branding, and links, but is served from the unrelated domain 2251176648.hydr0.org. The hydr0.org domain is a numerically-prefixed subdomain with no visible affiliation to mp3.cc, creating a convincing lookalike that could deceive users into trusting the site as the genuine mp3.cc. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:33-36 (logo/branding), metadata.json domain)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net, a third-party proxy domain, rather than being served directly from mp3.cc or the hosting domain. The sunproxy.net domain acts as an intermediary for all media delivery, and the file paths contain long opaque base64-encoded strings that obscure the actual file destinations. This is consistent with traffic interception or surveillance of user media consumption. (location: page.html:228,247,266,285 (data-url attributes on playlist-play anchors) — all 40+ song entries)
hidden content
Audio file download URLs embed long base64-encoded path components (e.g., NDgwdkFuTUxJZ0tH...) that encode the actual file routing parameters opaquely. The scanner flagged 12 suspicious base64 blobs. These blobs are used in every media URL routed through fine.sunproxy.net and obscure the true file paths, preventing transparent inspection of where files originate or what parameters are passed to the proxy. (location: page.html:228,247,266 etc. (data-url attributes) — all playlist-play href data-url values)
curl https://api.brin.sh/domain/2251176648.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2251176648.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.