context safety score
A score of 70/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The page is served from htoto.hydr0.org (a subdomain using a zero '0' instead of the letter 'o' in 'hydro') but displays full MP3.cc branding, logo, stylesheet, scripts, and copyright notice ('© 2017–2026 MP3.cc'). The domain uses a homoglyph/typosquat technique ('hydr0' vs 'hydro') to masquerade as a legitimate MP3.cc mirror or affiliate while operating under a deceptive domain. (location: page.html:5,9,11,14,33,34 — title tag, canonical link, og:site_name, og:url, logo href; metadata.json domain field)
malicious redirect
The canonical URL declared in the page (https://mp3.cc/t/656081533-htoto/) differs from the actual serving domain (htoto.hydr0.org). The brin-context also reports 1 redirect detected. The page silently pulls all assets (CSS, JS, fonts) from mp3.cc while being hosted on a separate suspicious domain, indicating the site acts as an unauthorized proxy or redirect layer for the legitimate service. (location: page.html:9 (canonical href), page.html:18-19 (cross-domain asset loads), .brin-context.md line 19 (Redirects: 1))
brand impersonation
All functional links (genres, footer navigation, share buttons, logo) point back to mp3.cc, making the page appear to be an official MP3.cc page while the actual hosting domain is the deceptive hydr0.org. This could be used to intercept traffic intended for mp3.cc or to serve a manipulated version of the site to specific user agents (user-agent diff ratio of 0.39 detected, suggesting different content served to bots vs browsers). (location: page.html:33,59,73,87,101,118,131,145,164,175,188,229-231; .brin-context.md line 23 (user-agent diff ratio: 0.39))
social engineering
The contact email listed in the footer (hydrofm@yandex.com) uses a Yandex address associated with a domain that employs homoglyph deception (hydr0). Users contacting this address may believe they are reaching the legitimate MP3.cc support team. Combining a Russian-hosted email service with a deceptive domain increases the social engineering risk. (location: page.html:234 (footer copyright div))
curl https://api.brin.sh/domain/htoto.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
htoto.hydr0.org currently scores 70/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.