context safety score
A score of 68/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 scanned URL https://2354172211.hydr0.org redirected to and served content for mp3.cc, a third-party music download site. The subdomain 2354172211.hydr0.org is not mp3.cc, but the page presents itself entirely as MP3.cc including canonical tags, og:url, og:site_name, all internal links, and copyright notices. This is a redirect/cloaking arrangement where the hosting domain (hydr0.org) proxies or mirrors mp3.cc content under a numeric subdomain. (location: metadata.json: url=https://2354172211.hydr0.org; page.html line 9: canonical href=https://mp3.cc/; line 14: og:url=https://mp3.cc/)
brand impersonation
The page fully impersonates MP3.cc — including its logo, branding, site name, copyright notice, and canonical URL — while being served from the unrelated domain 2354172211.hydr0.org. Users or agents visiting this URL would believe they are on mp3.cc when they are not. The footer also displays the contact email hydrofm@yandex.com, associating MP3.cc's brand with a Yandex email address not affiliated with the legitimate site. (location: page.html line 5: title 'MP3.cc'; line 9: canonical mp3.cc; line 1184: copyright mp3.cc with hydrofm@yandex.com)
malicious redirect
All audio file play links resolve through the third-party proxy domain fine.sunproxy.net rather than mp3.cc directly. The data-url attributes in every playlist item point to fine.sunproxy.net/file/ with base64-encoded path parameters. This intermediary proxy domain is unrelated to both the scanned host and mp3.cc, and could be used for traffic interception, user tracking, or serving malicious payloads in place of legitimate MP3 files. (location: page.html lines 228, 247, 266, 285, etc.: data-url='https://fine.sunproxy.net/file/...')
hidden content
The base64-encoded path segments in the fine.sunproxy.net file URLs (12 flagged by Tier 2 scanner) encode opaque data passed to the proxy. While individually these appear to be signed/tokenized file paths, the pattern of routing all media through an obfuscated base64 token to a third-party domain prevents content verification and obscures the actual file source. (location: page.html: all data-url attributes containing base64 strings in fine.sunproxy.net/file/ paths)
curl https://api.brin.sh/domain/2354172211.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2354172211.hydr0.org currently scores 68/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.