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 scanned URL (24-28hz-2pac-feat-big-syke.hydr0.org) is a subdomain that mirrors the content of mp3.cc, with a canonical tag pointing to mp3.cc and all internal links directing to mp3.cc. The page was reached via a redirect (1 redirect noted in pre-scan), indicating the subdomain acts as a redirect/doorway page funneling users to the mp3.cc domain. (location: page.html:9 - canonical href and all navigation links pointing to https://mp3.cc/)
brand impersonation
The site at hydr0.org subdomain presents itself as MP3.cc (title, logo, branding, and all content identical to mp3.cc) without being the legitimate mp3.cc domain. The subdomain 24-28hz-2pac-feat-big-syke.hydr0.org impersonates the MP3.cc brand while operating under the hydr0.org domain, which could deceive users into believing they are on the legitimate site. (location: page.html:5 - title tag; page.html:11 - og:site_name meta tag; page.html:33-36 - logo link)
malicious redirect
All MP3 audio file downloads are served through a third-party proxy domain (fine.sunproxy.net) using opaque base64-encoded file path tokens. This constitutes the 12 suspicious base64 blobs flagged in pre-scan. While possibly a CDN arrangement, routing downloads through an intermediary proxy with encoded URLs obscures the actual file destinations and could facilitate tracking or serve malicious files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes pointing to https://fine.sunproxy.net/file/[base64])
hidden content
The deceptive link flagged in pre-scan corresponds to the 'Online Radio' link (line 204) which uses class 'z__important' and targets looz.net in a new tab (_blank). This is an off-brand external link embedded among genre navigation links that could redirect users to an unrelated third-party site without clear disclosure. (location: page.html:204 - <a href="https://looz.net/" class="z__important no-ajax" target="_blank">Online Radio</a>)
curl https://api.brin.sh/domain/24-28hz-2pac-feat-big-syke.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
24-28hz-2pac-feat-big-syke.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.