context safety score
A score of 71/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
The page is hosted on anisha-ranghar-arvind-raj-sunwal.hydr0.org but declares a canonical URL of https://mp3.cc/t/3672892052-anisha-ranghar-arvind-raj-sunwal/. The domain hydr0.org is serving content that impersonates mp3.cc, and the pre-scan context flags 1 redirect with a user-agent differential ratio of 0.49, indicating the site may serve different content to bots vs. browsers (cloaking). (location: <link rel="canonical" href="https://mp3.cc/..."> in page.html:9; .brin-context.md: redirects=1, user-agent diff ratio=0.49)
brand impersonation
The hydr0.org subdomain fully replicates the MP3.cc website — including its logo, CSS, JavaScript, layout, genre sidebar, footer copyright, and all internal links pointing to mp3.cc. The site presents itself as MP3.cc while being hosted on a third-party domain (hydr0.org), deceiving users and AI agents into believing they are interacting with the legitimate mp3.cc service. (location: page.html:5 (title), page.html:11 (og:site_name='MP3.cc'), page.html:33-36 (logo), page.html:253 (footer copyright MP3.cc))
malicious redirect
Audio playback is routed through a third-party proxy domain fine.sunproxy.net rather than the purported mp3.cc origin. The URL path contains a base64-encoded blob which decodes to binary/obfuscated parameters, consistent with a token-based proxy that could log user interactions, substitute content, or redirect to malicious payloads. (location: page.html:228, data-url attribute pointing to https://fine.sunproxy.net/file/<base64>/...mp3)
obfuscated code
The audio file URL path on fine.sunproxy.net contains a base64-encoded segment (NDgwdkFuTUxJZ0tH...) which decodes to binary data with non-printable characters, obscuring the actual routing parameters. This obfuscation hides the true destination or access token from inspection tools. (location: page.html:228, data-url path segment: NDgwdkFuTUxJZ0tHbEJUVFE0QUZzeU50Smt3cnFoanUyVFdycUE0OVNpQnNvK3llc2hJZnQ4d3FIMDZwazFra1VUL3dFM1Z1R2lWVkgrbytza3dhNTJmSStncTVFbGFWaW92ZUZObWpabXc9)
curl https://api.brin.sh/domain/anisha-ranghar-arvind-raj-sunwal.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anisha-ranghar-arvind-raj-sunwal.hydr0.org currently scores 71/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.