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 domain dr-tarik.hydr0.org serves a full clone of MP3.cc, reusing its branding, logo, title ('Dr Tarik | Download mp3 free, listen music online - MP3.cc'), CSS, JavaScript, and copyright notice verbatim. All navigation links and download links point back to mp3.cc, making the page appear to be an official MP3.cc property while being hosted on an unrelated third-party domain. (location: page.html:5 (title), page.html:9 (canonical), page.html:18-19 (assets from mp3.cc), page.html:348 (footer copyright))
malicious redirect
Audio stream URLs in data-url attributes route all playback through the third-party proxy fine.sunproxy.net rather than the canonical source. The canonical meta tag points to mp3.cc while the page is served from hydr0.org, and one HTTP-level redirect was observed during crawl. This proxy interception can be used to log listener activity, substitute content, or serve malware payloads in place of audio files. (location: page.html:228,247,266,285,304,323 (data-url attributes via fine.sunproxy.net); page.html:9 (canonical redirect to mp3.cc))
obfuscated code
Six data-url attribute values contain double-encoded base64 blobs that, when decoded, yield a second layer of base64 which resolves to binary data rather than a plain URL path. This two-layer encoding obscures the actual audio resource paths served by fine.sunproxy.net, preventing straightforward inspection of the proxied content destination and evading URL-based security filters. (location: page.html:228,247,266,285,304,323 (data-url base64 blobs in playlist-play anchors))
social engineering
The footer displays copyright attributed to 'MP3.cc' (a legitimate brand) but lists a contact address of hydrofm@yandex.com — a Yandex (Russian webmail) address unaffiliated with mp3.cc. This mismatch between a well-known brand attribution and an anonymous third-party email is a classic trust-building deception. The 'Online Radio' sidebar link also redirects to an entirely separate external domain (looz.net) styled identically to mp3.cc navigation items, without disclosure. (location: page.html:348 (footer: hydrofm@yandex.com); page.html:204 (looz.net link))
curl https://api.brin.sh/domain/dr-tarik.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-tarik.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.