context safety score
A score of 65/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
The page is served from era-cold-song.hydr0.org but displays MP3.cc branding throughout, including the page title ('Download mp3 free, listen music online - MP3.cc'), the logo, and footer copyright ('© 2017–2026 MP3.cc'). All navigation links and canonical tags point to mp3.cc. The site loads CSS and JS assets directly from mp3.cc. This is a hydr0.org-operated mirror that presents itself as the legitimate MP3.cc service, confusing users about which site they are actually using. (location: page.html:5 (title), page.html:9 (canonical), page.html:18-19 (asset loading), page.html:557 (footer copyright))
malicious redirect
The page includes a canonical link redirecting to https://mp3.cc/t/1986312064-era-cold-song/ from the actual serving domain era-cold-song.hydr0.org. This canonical redirect combined with all navigation links pointing to mp3.cc means any user or search engine following canonical signals is silently redirected to a different domain than the one they are on. This matches the single redirect flagged in Tier 2 analysis. (location: page.html:9 (rel=canonical href='https://mp3.cc/t/1986312064-era-cold-song/'))
obfuscated code
All 17 media file play URLs are base64-encoded values stored in data-url attributes pointing to fine.sunproxy.net. The base64 decodes to binary/encrypted data rather than plain URLs, obscuring the actual media source and proxy routing. The 12 suspicious base64 blobs flagged in Tier 2 correspond to these encoded proxy URLs. While this may be a DRM or anti-hotlinking mechanism, the use of a third-party proxy domain (fine.sunproxy.net) with opaque encoded payloads is a notable obfuscation pattern. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532 (data-url attributes))
curl https://api.brin.sh/domain/era-cold-song.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
era-cold-song.hydr0.org currently scores 65/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.