context safety score
A score of 61/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
brand impersonation
The page is served from hydr0.org (dilby-pornbugs-hold-the-line.hydr0.org) but fully impersonates MP3.cc: the HTML title reads 'Download mp3 free, listen music online - MP3.cc', og:site_name is 'MP3.cc', the canonical link points to mp3.cc, all navigation and footer links reference mp3.cc, and the footer copyright reads '© 2017–2026 MP3.cc'. The site is an unauthorized mirror/clone presenting itself as the legitimate MP3.cc brand. (location: page.html:5,9,11,14,272 — title, canonical, og:site_name, og:url, footer copyright)
malicious redirect
One redirect was detected (per brin-context Redirects: 1). The scanned URL is dilby-pornbugs-hold-the-line.hydr0.org but all canonical and Open Graph metadata redirect attribution to mp3.cc, masking the true serving origin and potentially redirecting users or crawlers away from the actual host. (location: metadata.json / .brin-context.md (Redirects: 1); page.html:9 canonical href)
malicious redirect
All MP3 audio file downloads are routed through a third-party proxy domain (fine.sunproxy.net) using double-encoded, encrypted binary tokens embedded in URLs. This off-domain media proxy could intercept, replace, or monetize file downloads without user awareness. The proxy domain is unrelated to either hydr0.org or mp3.cc. (location: page.html:228 — data-url https://fine.sunproxy.net/file/YVlGMW...; page.html:247 — data-url https://fine.sunproxy.net/file/YVlGMW...)
hidden content
Two suspicious base64 blobs were flagged by Tier 2 analysis. Decoded, they are double-encoded binary (encrypted) tokens used as file-access keys in the fine.sunproxy.net media proxy URLs. While not plaintext injection, the use of opaque encrypted tokens in client-side URLs obscures the true file source and destination routing from both users and security tools. (location: page.html:228,247 — data-url attributes containing base64-within-base64 encrypted tokens)
social engineering
The page uses a robots meta tag 'noarchive' to prevent web archiving (e.g., Wayback Machine), which is a common evasion tactic used by piracy and fraudulent sites to avoid historical evidence of their content being preserved. Combined with impersonation of MP3.cc, this reduces accountability. (location: page.html:8 — <meta name="robots" content="noarchive">)
curl https://api.brin.sh/domain/dilby-pornbugs-hold-the-line.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dilby-pornbugs-hold-the-line.hydr0.org currently scores 61/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.