context safety score
A score of 53/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
3 deceptive links where visible host does not match destination host
malicious redirect
The page is served from subdomain anitta-becky-g.hydr0.org but all canonical links, CSS, JS, images, and navigation links point to mp3.cc. The subdomain acts as a redirect/proxy front for mp3.cc content, presenting mp3.cc branding and assets while the actual serving domain differs. The canonical tag (line 9) explicitly states https://mp3.cc/t/326426661-anitta-becky-g/ as the authoritative URL, indicating the serving domain is not the legitimate one. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/326426661-anitta-becky-g/">)
brand impersonation
The site at anitta-becky-g.hydr0.org presents itself fully as MP3.cc — using MP3.cc's logo, branding, CSS, JavaScript, and OG metadata (og:site_name=MP3.cc, og:url pointing to mp3.cc). The serving domain hydr0.org is not mp3.cc, constituting brand impersonation of the MP3.cc service. (location: page.html:5,11,14,18,19,33)
malicious redirect
All 20 audio file URLs use the domain fine.sunproxy.net as a proxy/relay layer with long base64-encoded path tokens. These are not direct mp3.cc file links — user audio requests are routed through an unknown third-party proxy (sunproxy.net), which could intercept traffic, serve malware-laced files, or track users. The base64-encoded path segments (12 suspicious blobs flagged in Tier 2) correspond to these opaque proxy file tokens. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 - data-url attributes pointing to fine.sunproxy.net)
social engineering
The page title and metadata claim to offer free MP3 downloads ('Download mp3 free, listen music online - MP3.cc') while the actual domain is a third-party subdomain (hydr0.org) proxying the content. Users are led to believe they are on the official MP3.cc site when they are not, which could be used to build trust before serving malicious content or ads. (location: page.html:5 - <title>Anitta Becky G | Download mp3 free, listen music online - MP3.cc</title>)
curl https://api.brin.sh/domain/anitta-becky-g.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anitta-becky-g.hydr0.org currently scores 53/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.