context safety score
A score of 51/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
brand impersonation
Page is served from cd3-binary-finary.hydr0.org but fully impersonates MP3.cc: title reads 'MP3.cc', og:site_name is 'MP3.cc', canonical URL points to mp3.cc, CSS/JS assets load from mp3.cc, and the logo links to mp3.cc. This is an unauthorized mirror/clone of the legitimate MP3.cc website. (location: page.html:5-9, lines 11-14, 18-19, 33-36)
malicious redirect
The serving domain cd3-binary-finary.hydr0.org involves 1 redirect (noted in pre-scan context). All audio playback is silently routed through fine.sunproxy.net via obfuscated base64-token URLs in data-url attributes, redirecting media requests through an unverified third-party proxy rather than the canonical mp3.cc infrastructure. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589)
obfuscated code
All 19 audio stream URLs (data-url attributes) route through fine.sunproxy.net using long base64-encoded path tokens (12 unique blobs flagged in pre-scan). The base64 tokens decode to binary/encrypted data, obscuring the true file origin and bypassing direct attribution to mp3.cc. This pattern is consistent with traffic interception or unauthorized proxying. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589)
social engineering
The 'Online Radio' sidebar link (href=https://looz.net/) is styled with the class 'z__important' and opens in a new tab (target='_blank'), visually embedded among legitimate genre navigation links. This deceptive placement encourages clicks on an external unrelated domain, flagged as a deceptive link in pre-scan analysis. (location: page.html:204-215)
hidden content
An HTML comment at the end of the page leaks server-side timing and geolocation metadata: '0.741752; 1 (0.0007469654083252). (US|).', disclosing render time and likely user/session geolocation data to anyone inspecting the source. (location: page.html:695)
curl https://api.brin.sh/domain/cd3-binary-finary.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
cd3-binary-finary.hydr0.org currently scores 51/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.