context safety score
A score of 72/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The domain era-don-t-go-away.hydr0.org redirects to mp3.cc content (canonical URL points to https://mp3.cc/t/1742299986-era-don-t-go-away/). The subdomain is constructed to mimic a song title search but operates as a redirect/proxy to mp3.cc, potentially used to disguise the true destination or bypass blocklists. The brin-context confirms 1 redirect was detected. (location: <link rel='canonical' href='https://mp3.cc/t/1742299986-era-don-t-go-away/'> and metadata domain: era-don-t-go-away.hydr0.org)
brand impersonation
The page fully renders as MP3.cc (title, logo, branding, footer copyright '© 2017 – 2026 MP3.cc') while being served from the unrelated domain era-don-t-go-away.hydr0.org under hydr0.org. This constitutes impersonation of the MP3.cc brand via a lookalike/proxy domain. (location: page.html line 5 (<title>), line 652 (footer copyright), domain era-don-t-go-away.hydr0.org)
malicious redirect
All audio file download/play URLs route through fine.sunproxy.net, a third-party proxy service not affiliated with mp3.cc. The base64-encoded file paths (12 suspicious blobs flagged in Tier 2) in data-url attributes obscure the actual file destinations. Users clicking play/download are routed through this proxy without disclosure. (location: page.html lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589, 608, 627 (data-url attributes on playlist-play anchors))
hidden content
The base64 strings embedded in the sunproxy.net file URLs (12 flagged blobs) encode opaque routing tokens that are not human-readable and cannot be verified without decoding. While consistent with a proxy file-serving scheme, they obscure the true file origin and could encode additional redirect or tracking parameters. (location: page.html data-url attributes on all playlist-play anchor elements (e.g., lines 228, 247, 266, etc.))
curl https://api.brin.sh/domain/era-don-t-go-away.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
era-don-t-go-away.hydr0.org currently scores 72/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.