context safety score
A score of 62/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted at emre-kabak.hydr0.org but contains a canonical URL pointing to mp3.cc and all navigation/resource links point to mp3.cc. The subdomain hydr0.org acts as a redirect/proxy facade for mp3.cc content, confirmed by the Tier 2 signal of 1 redirect detected. Audio files are served via fine.sunproxy.net, a third-party proxy domain not affiliated with the displayed brand, routing media traffic through an unknown intermediary. (location: page.html:9 (canonical href), page.html:228 (data-url attributes pointing to fine.sunproxy.net))
brand impersonation
The site emre-kabak.hydr0.org presents itself with full MP3.cc branding, logo, layout, CSS, and JavaScript loaded entirely from mp3.cc. The hosting domain (hydr0.org) is unrelated to the brand being displayed, creating a deceptive appearance that the page is legitimately part of mp3.cc when it is not. This pattern is consistent with a mirror/clone site used to serve content under a different domain while impersonating an established brand. (location: page.html:5 (title tag), page.html:11 (og:site_name), page.html:18-19 (CSS/JS from mp3.cc), page.html:33 (logo href))
malicious redirect
Tier 2 scan flagged 1 deceptive link. The 'Online Radio' sidebar link points to looz.net (an external domain unrelated to mp3.cc) with target='_blank', embedded within what appears to be the mp3.cc navigation. This external outbound link is styled identically to internal navigation links, obscuring its off-domain nature. (location: page.html:204 (href=https://looz.net/, class=z__important, target=_blank))
hidden content
Twelve suspicious base64 blobs were flagged by Tier 2 analysis. All base64 strings are present in data-url attributes of playlist play links and decode to encoded MP3 file paths served via fine.sunproxy.net. While these are functional obfuscated media URLs rather than injected payloads, they route audio delivery through an opaque proxy (fine.sunproxy.net) whose encoded paths obscure the true file origin and prevent direct URL inspection. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 (data-url attributes with base64-encoded paths))
curl https://api.brin.sh/domain/emre-kabak.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
emre-kabak.hydr0.org currently scores 62/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.