context safety score
A score of 54/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 page is hosted on 'hydr0.org' (a subdomain) but all canonical URLs, CSS, JS, and links point to 'mp3.cc'. The canonical tag explicitly redirects to https://mp3.cc/t/1147340067-bassjackers-ft-luciana-jason-risk-jacob-rodi/, indicating this subdomain acts as a redirect/proxy doorway page for mp3.cc — a site known for serving copyrighted MP3s without authorization. The hydr0.org domain functions as a shadow domain funneling traffic. (location: page.html:9 - <link rel='canonical' href='https://mp3.cc/t/...'/>)
malicious redirect
All audio file URLs (12 total) use 'fine.sunproxy.net' as a proxy intermediary to serve MP3 files. The 'sunproxy.net' domain is a third-party proxy/CDN not affiliated with mp3.cc, used to obscure the true origin of the audio files and bypass direct linking restrictions. This represents an unauthorized content proxy that could be used to deliver malware-laced files or track users. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570 - data-url attributes pointing to fine.sunproxy.net)
brand impersonation
The page is served from 'bassjackers-ft-luciana-jason-risk-jacob-rodi.hydr0.org' but presents itself as 'MP3.cc' with full MP3.cc branding, logo, styles, and navigation. The hydr0.org domain impersonates the MP3.cc service by mirroring its content and UI, misleading users into believing they are on the legitimate mp3.cc website. The footer even contains mp3.cc's copyright notice and contact email. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:595 (footer copyright))
malicious redirect
The 12 base64-encoded blob strings in the audio data-url attributes on fine.sunproxy.net are obfuscated file paths. While flagged by Tier 2 as 'suspicious base64 blobs: 12', these encode proxy routing parameters to obscure the actual file source and destination, consistent with evasion of content scanning and URL filtering. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - NDgwdkFuTUx... base64 strings in fine.sunproxy.net URLs)
curl https://api.brin.sh/domain/bassjackers-ft-luciana-jason-risk-jacob-rodi.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bassjackers-ft-luciana-jason-risk-jacob-rodi.hydr0.org currently scores 54/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.