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.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The page is served from hydr0.org but fully impersonates MP3.cc: the title tag reads 'MP3.cc', og:site_name is 'MP3.cc', the canonical URL points to mp3.cc, and all navigation/footer links resolve to mp3.cc. Users visiting the hydr0.org domain are presented with a convincing clone of a third-party brand. (location: page.html:5-14, page.html:33-36, page.html:652)
malicious redirect
The brin-context metadata records 1 redirect occurring before landing on this page. The site also sets 'meta robots: noarchive' to suppress search-engine caching, a common evasion tactic used by phishing and piracy mirror sites to avoid archival and detection. (location: .brin-context.md (Redirects: 1), page.html:8)
obfuscated code
All 12 audio stream URLs use base64-encoded opaque tokens routed through the third-party proxy fine.sunproxy.net. The decoded payloads are binary cipher blobs (not plain URLs), effectively hiding the true destination of media file requests and preventing straightforward URL inspection. This is consistent with obfuscated link routing used to evade content filters. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437 (all data-url attributes))
curl https://api.brin.sh/domain/british-military-march-the-british-grenadiers.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
british-military-march-the-british-grenadiers.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.