context safety score
A score of 60/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
17 deceptive links where visible host does not match destination host
malicious redirect
The domain dr-won.hydr0.org redirects to mp3.cc content (canonical URL https://mp3.cc/t/1864922808-dr-won/), presenting content belonging to a different domain. The subdomain hydr0.org is used as a proxy/mirror for mp3.cc, which is a known piracy/copyright-infringing MP3 download site. This redirect pattern (1 redirect detected in pre-scan) routes users from the landing domain to a third-party service without clear disclosure. (location: page.html:9 - canonical href and overall page redirect pattern)
brand impersonation
The page at dr-won.hydr0.org fully reproduces the MP3.cc brand identity including its logo, site name, CSS/JS assets, copyright notice '© 2017–2026 MP3.cc', and contact email 'hydrofm@yandex.com'. All assets are loaded from mp3.cc. The hosting domain (hydr0.org) is distinct from the brand domain (mp3.cc), creating a brand impersonation scenario where the subdomain masquerades as or proxies the MP3.cc service. (location: page.html:5,11,18,19,33,35,671)
malicious redirect
All 17 audio file play URLs use a proxy service at fine.sunproxy.net with long base64-encoded path parameters (12 suspicious base64 blobs detected in pre-scan). The sunproxy.net domain acts as an intermediary file proxy, routing MP3 download traffic through a third-party server. This obfuscates the true origin of files and could facilitate tracking, traffic interception, or malware delivery via audio file downloads. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 - data-url attributes pointing to fine.sunproxy.net)
curl https://api.brin.sh/domain/dr-won.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-won.hydr0.org currently scores 60/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.