context safety score
A score of 50/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The domain atl-ft-l-one.hydr0.org serves content that is a full clone/mirror of mp3.cc, a third-party music download site. The canonical URL in the page head points to https://mp3.cc/t/1475866582-atl-ft-l-one/, and all internal links, assets (CSS, JS), and branding resolve to mp3.cc. The visiting domain (hydr0.org subdomain) redirects/proxies users to mp3.cc content without disclosure, consistent with a cloaking or traffic-redirect operation. One redirect was confirmed by pre-scan signals. (location: <link rel='canonical' href='https://mp3.cc/t/1475866582-atl-ft-l-one/'> and all asset hrefs in page.html head)
brand impersonation
The page fully impersonates the MP3.cc brand — including its logo, site name, copyright notice ('© 2017 – 2026 MP3.cc'), navigation, and layout — while being served from the unrelated domain atl-ft-l-one.hydr0.org. Users and AI agents browsing this URL would believe they are interacting with the legitimate MP3.cc website. (location: page.html: <title>, <meta og:site_name>, header logo, footer #foo-copyright)
malicious redirect
All audio file streaming URLs are routed through the third-party proxy domain fine.sunproxy.net using base64-encoded path parameters (e.g., NDgwdkFuTUxJZ0tH...). This is a known pattern for proxying/obfuscating the true origin of served files and potentially tracking or redirecting users. The 12 'suspicious base64 blobs' flagged in pre-scan correspond to these encoded file paths in data-url attributes. (location: page.html: all playlist-play <a> elements with data-url='https://fine.sunproxy.net/file/...')
brand impersonation
MP3 file names served through fine.sunproxy.net embed the 'Hydr0.org' brand in parentheses (e.g., 'ATL_feat._L_One_-_Kislorod_(Hydr0.org).mp3'), indicating these files were repackaged or re-labeled by the hydr0.org operator to associate themselves with the content, potentially for SEO manipulation or traffic attribution fraud. (location: page.html: data-url filenames across all playlist-play elements)
malicious redirect
The sidebar contains an outbound link to looz.net (labeled 'Online Radio') styled with class 'z__important', which opens in a new tab via target='_blank'. This is the one 'deceptive link' flagged in pre-scan. The link destination (looz.net) is unrelated to MP3.cc and may be an affiliate redirect or ad-network destination embedded within the cloned site. (location: page.html line 204: <a href='https://looz.net/' class='z__important no-ajax' target='_blank'>Online Radio</a>)
curl https://api.brin.sh/domain/atl-ft-l-one.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
atl-ft-l-one.hydr0.org currently scores 50/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.