context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The scanned URL is bob-chilcott.hydr0.org but the page content, canonical tag, og:url, and all internal links point to mp3.cc. The site is serving a full mp3.cc mirror/clone on a different domain (hydr0.org subdomain), indicating a redirect/cloaking arrangement where users landing on hydr0.org are presented with content branded as mp3.cc without being transparently redirected to the legitimate domain. (location: page.html:9 (<link rel="canonical" href="https://mp3.cc/t/545439898-bob-chilcott/">) and page.html:14 (<meta property="og:url" content="https://mp3.cc/t/545439898-bob-chilcott/"/>))
brand impersonation
The page fully impersonates the MP3.cc brand — including logo, site name, navigation, footer copyright '© 2017–2026 MP3.cc', and all styling — while being hosted on the unrelated domain bob-chilcott.hydr0.org. This constitutes brand impersonation of MP3.cc by a third-party domain operator. (location: page.html:5 (title tag), page.html:614 (footer copyright), page.html:33-36 (logo link to mp3.cc))
malicious redirect
All audio file URLs use the third-party proxy domain fine.sunproxy.net with base64-encoded path parameters. Media is not served from mp3.cc directly but routed through an opaque proxy, which could intercept traffic, serve malware via the audio endpoint, or track users. The base64 blobs in the URLs (12 flagged by scanner) encode obfuscated file paths passed to this proxy. (location: page.html:228 (data-url="https://fine.sunproxy.net/file/NDgw...") and all subsequent playlist-play anchors)
hidden content
The page contains a server-side timing/debug comment at the very end of the HTML outside the closing </html> tag: '<!-- 0.867687; 1 (0.00061988830566406). (US|). -->'. This leaks server performance metrics and geo-targeting data (US region indicator) in an HTML comment, suggesting server-side user profiling or geo-based content delivery. (location: page.html:695 (<!-- 0.867687; 1 (0.00061988830566406). (US|). -->))
social engineering
The page presents itself as a legitimate free MP3 download site (MP3.cc clone), encouraging users to download copyrighted music files through an unlicensed third-party proxy (fine.sunproxy.net). This is a social engineering vector that lures users into downloading files from an untrusted proxy under the guise of a known music service. (location: page.html:228-603 (all playlist download/play links routing through fine.sunproxy.net))
curl https://api.brin.sh/domain/bob-chilcott.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bob-chilcott.hydr0.org currently scores 49/100 with a suspicious 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.