context safety score
A score of 65/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 domain ain-t-it-fun.hydr0.org serves a page that clones the visual identity, layout, CSS, and JavaScript of mp3.cc (including logo, canonical URLs, og:site_name, and footer copyright). All static assets (CSS, JS, images) are loaded from mp3.cc, and canonical links point to mp3.cc, while the serving domain is the unrelated hydr0.org subdomain. This constitutes brand impersonation of the legitimate MP3.cc service. (location: page.html:5,9,11,18,19,33 — title, canonical, og:site_name, stylesheet, script all reference mp3.cc from ain-t-it-fun.hydr0.org)
malicious redirect
All 12+ MP3 play URLs route audio file requests through fine.sunproxy.net, a third-party proxy domain, rather than mp3.cc directly. The base64-encoded path parameters (12 suspicious blobs flagged in Tier 2) are opaque file tokens passed to this proxy. This intermediary proxy could log user interactions, substitute files, or redirect to malicious payloads. Users clicking play are routed through an unverifiable third-party proxy. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608 — data-url attributes pointing to fine.sunproxy.net)
social engineering
The page presents itself as a legitimate free MP3 download site mirroring mp3.cc content, offering copyrighted music (Paramore, Guns N' Roses, Dead Boys) as free downloads. This lures users into downloading files through an untrusted proxy (fine.sunproxy.net) under the guise of a trusted brand. The contact email hydrofm@yandex.com in the footer uses a Yandex address inconsistent with a US/international music service, suggesting the operator is obscuring their identity. (location: page.html:633 — footer copyright with hydrofm@yandex.com; page.html:228-622 — free download links for copyrighted content via proxy)
curl https://api.brin.sh/domain/ain-t-it-fun.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
ain-t-it-fun.hydr0.org currently scores 65/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.