context safety score
A score of 55/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 on bruno-martini-iza-timbaland.hydr0.org but its canonical URL, all internal links, CSS, JS, and social-share targets all point to mp3.cc. The hydr0.org domain acts as a redirect/proxy mirror for mp3.cc content, confirmed by the Tier-2 signal of 1 redirect. Users and agents arriving at hydr0.org are transparently served mp3.cc content under a different domain, masking the true origin. (location: page.html:9 (canonical href), page.html:18-19 (external asset loading), metadata.json (domain vs. canonical mismatch))
brand impersonation
The page fully impersonates the MP3.cc brand — including its logo, site name, navigation, footer copyright, and all UI elements — while being served from the unrelated domain hydr0.org. The page title reads 'MP3.cc' and the footer asserts '© 2017–2026 MP3.cc', creating a convincing but deceptive brand clone on a third-party domain. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:424 (footer copyright), metadata.json (domain: hydr0.org))
malicious redirect
All MP3 audio files are served via fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc. The data-url attributes in playlist play buttons route audio downloads through this external proxy, which could intercept, log, or manipulate traffic. This is the source of the 10 suspicious base64 blobs flagged in Tier-2, as each data-url contains a long base64-encoded token. (location: page.html:228,247,266,285,304,323,342,361,380,399 (data-url attributes pointing to fine.sunproxy.net))
social engineering
The site presents itself as a legitimate free MP3 download service offering copyrighted music tracks (Bruno Martini, IZA, Timbaland) for free download. This is a common lure used to attract users to piracy/proxy sites that may serve malware, ads, or collect data. The contact email hydrofm@yandex.com (Yandex-hosted) in the footer is inconsistent with a legitimate Western music service. (location: page.html:424 (footer: hydrofm@yandex.com), page.html:229,248,267 (download links for copyrighted music))
hidden content
The HTML comment at line 505 leaks internal server performance/routing metadata: '1.116458; 1 (0.00057196617126465). (US|).' This discloses server-side timing and geolocation routing data, which could assist attackers in fingerprinting server infrastructure. (location: page.html:505 (HTML comment after closing </html> tag))
curl https://api.brin.sh/domain/bruno-martini-iza-timbaland.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bruno-martini-iza-timbaland.hydr0.org currently scores 55/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.