context safety score
A score of 53/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
brand impersonation
The page is served from dabzee.hydr0.org but renders entirely as MP3.cc (title, logo, canonical URL, og:site_name, copyright). The subdomain 'hydr0' uses a zero ('0') in place of the letter 'o' to mimic 'hydro', a classic homoglyph/typosquatting technique. The site passes itself off as MP3.cc while operating under a deceptive lookalike domain. (location: page.html:5,9,11,14 — <title>, canonical href, og:site_name, og:url)
malicious redirect
The canonical tag redirects to https://mp3.cc/t/479242509-dabzee/ and all internal navigation links point to mp3.cc, meaning the actual serving domain (dabzee.hydr0.org) is masked. The brin-context reports 1 redirect. Users or crawlers landing on dabzee.hydr0.org are silently served content attributed to mp3.cc, obscuring the true origin. (location: page.html:9 — <link rel="canonical" href="https://mp3.cc/t/479242509-dabzee/">)
malicious redirect
All audio file URLs resolve through fine.sunproxy.net, a third-party proxy not affiliated with MP3.cc. The base64-encoded path segments (12 suspicious blobs flagged by Tier 2) are the opaque file tokens passed to this proxy. Routing media through an uncontrolled proxy allows the operator of sunproxy.net to intercept requests, log user IPs/behavior, serve alternate payloads, or redirect to malicious content. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 — data-url attributes pointing to fine.sunproxy.net)
hidden content
MP3 filenames embedded in the sunproxy.net data-url attributes contain '(Hydr0.org)' as a parenthetical tag (e.g., 'V3K_Moeha_Dabzee_-_Bharavase_(Hydr0.org).mp3'). This embeds the operator's brand identifier inside file download names, covertly attributing distributed content to hydr0.org and potentially used for tracking or SEO manipulation without user visibility. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 — mp3 filename parameters in data-url attributes)
curl https://api.brin.sh/domain/dabzee.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dabzee.hydr0.org currently scores 53/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.