context safety score
A score of 63/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 alau-toby-erbolat-erzhanbaev.hydr0.org but fully impersonates mp3.cc, reproducing its logo, navigation, branding, footer copyright, and layout. The canonical link redirects to the real mp3.cc domain, indicating the hydr0.org subdomain is a mirror/clone of the legitimate site. (location: page.html:5, page.html:9, page.html:11, page.html:33-36, page.html:253)
malicious redirect
The canonical tag on the impersonating domain points to https://mp3.cc/t/2228373578-alau-toby-erbolat-erzhanbaev/, redirecting users and search engines to the original mp3.cc. This is consistent with SEO cloaking or traffic interception behavior where the clone captures visits before passing them along. (location: page.html:9)
social engineering
The site presents a convincing music download interface under a subdomain (hydr0.org) mimicking mp3.cc to build user trust and induce clicks on play/download links that route through an off-domain proxy (fine.sunproxy.net). The deceptive branding is designed to make users believe they are on the legitimate mp3.cc service. (location: page.html:228-229, page.html:253)
obfuscated code
The MP3 audio play URL routes through fine.sunproxy.net and includes a large base64-encoded path segment that decodes to binary/encrypted data rather than a plain file path. This obfuscates the actual destination of the audio request and may be used to mask tracking, exfiltration endpoints, or payload delivery behind a proxy layer. (location: page.html:228 — data-url value: https://fine.sunproxy.net/file/NDgwdkFuTUxJZ0tHbEJUVFE0QUZzOWVPY2dxOHhOTFV6Nk1EQjlERng5M01KV2dxTUNrOTd1Wlp2dE5PSHZkampyQVZiQzBmV0ZLVHdOc2JaRktDQWlGY0w3QUlNcHVIcFpoR3pmSmxkdE09/...)
curl https://api.brin.sh/domain/alau-toby-erbolat-erzhanbaev.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
alau-toby-erbolat-erzhanbaev.hydr0.org currently scores 63/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.