context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The domain dr-steinman.hydr0.org serves content that canonically belongs to mp3.cc (canonical URL: https://mp3.cc/t/781633139-dr-steinman/). The page is a full mirror/proxy of mp3.cc content hosted on a different domain (hydr0.org), constituting an unauthorized redirect/proxy arrangement. A redirect (count: 1) was detected in pre-scan signals. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/781633139-dr-steinman/">)
brand impersonation
The site at dr-steinman.hydr0.org fully impersonates MP3.cc, reproducing its complete UI, branding, logo, stylesheets, and JavaScript from mp3.cc's CDN (mp3.cc/i/css/_main_min.css, mp3.cc/i/js/_main_min.js). All navigation, footer copyright, and content are presented under the MP3.cc brand while being served from an unrelated third-party domain (hydr0.org). (location: page.html:5,18,19,33-36,538)
malicious redirect
All audio file playback URLs resolve through 'fine.sunproxy.net', a third-party proxy/CDN not affiliated with mp3.cc. The filenames in the URLs contain long base64-encoded blobs (12 suspicious base64 blobs flagged in pre-scan). This intermediary intercepts all media requests and could be used for traffic monitoring, ad injection, or serving malicious payloads in place of legitimate audio files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513 - data-url attributes pointing to fine.sunproxy.net)
hidden content
The 12 suspicious base64 blobs embedded in the sunproxy.net file URLs are long encoded strings that obscure the actual file paths and parameters being passed to the proxy server. While these appear to be encoded file routing tokens, the obfuscation prevents transparent inspection of what data is being transmitted or requested from the proxy. (location: page.html - all data-url attributes, e.g. line 228: YVlGMWFTTXN3M0VjVThHdEhvZHd2aEUvN0prK0gv...)
social engineering
The site presents itself as a legitimate free MP3 download service (MP3.cc) while operating from a different domain (hydr0.org), potentially deceiving users into believing they are on the official MP3.cc site. The footer even displays the official mp3.cc copyright notice and contact email (hydrofm@yandex.com), reinforcing the deception. (location: page.html:538 - footer copyright; page.html:5 - title tag; page.html:11 - og:site_name)
curl https://api.brin.sh/domain/dr-steinman.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-steinman.hydr0.org currently scores 42/100 with a suspicious verdict and low 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.