context safety score
A score of 63/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 served from a subdomain 'clara-luciani-le-mur.hydr0.org' that impersonates a music search query but immediately redirects users to mp3.cc (canonical URL set to https://mp3.cc/t/820427255-clara-luciani-le-mur/). The subdomain acts as a redirect/proxy doorway page funneling traffic to the third-party site. The .brin-context.md confirms 1 redirect was detected. (location: page.html:9 - <link rel='canonical' href='https://mp3.cc/t/820427255-clara-luciani-le-mur/'>)
brand impersonation
The page at hydr0.org fully clones the MP3.cc website UI — including its logo, branding, CSS/JS assets loaded directly from mp3.cc, genre navigation, footer copyright '© 2017–2026 MP3.cc', and contact email 'hydrofm@yandex.com'. The hydr0.org domain is presenting itself as mp3.cc without being mp3.cc, constituting brand impersonation of the MP3.cc service. (location: page.html:5,18-19,33-36,671 - title, asset URLs, logo, footer)
malicious redirect
All MP3 file playback URLs route through 'fine.sunproxy.net', a third-party proxy/CDN domain not affiliated with mp3.cc. Audio files are served via obfuscated base64-encoded path tokens at fine.sunproxy.net/file/<base64>, allowing potential traffic interception, user tracking, or substitution of served content. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 - data-url attributes)
hidden content
The HTML comment at the bottom of the page '<!-- 0.904743; 1 (0.0005650520324707). (US|). -->' leaks server-side timing and geolocation metadata (US targeting) embedded as an HTML comment, suggesting server-side user profiling or geo-targeting infrastructure. (location: page.html:752 - HTML comment after closing </html> tag)
curl https://api.brin.sh/domain/clara-luciani-le-mur.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
clara-luciani-le-mur.hydr0.org currently scores 63/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.