context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
5 deceptive links where visible host does not match destination host
malicious redirect
The scanned URL (arianna-feat-pitbull-sexy-people.hydr0.org) does not serve its own content — it hosts a full clone/mirror of mp3.cc, impersonating the legitimate MP3.cc service. The canonical tag, all asset URLs, and all navigation links point back to mp3.cc, indicating this subdomain is a shadow copy used to intercept traffic and redirect users to third-party file proxy infrastructure. (location: page.html:9 — <link rel='canonical' href='https://mp3.cc/t/3503180308-arianna-feat-pitbull-sexy-people/'/>)
brand impersonation
The page fully impersonates MP3.cc (logo, branding, site structure, copyright notice '© 2017–2026 MP3.cc') while being served from the unrelated domain arianna-feat-pitbull-sexy-people.hydr0.org. All visual and structural elements are copied from the legitimate site without authorization, constituting brand impersonation to build false trust with visitors. (location: page.html:5,11,33-36,614)
malicious redirect
All audio file play links resolve through fine.sunproxy.net, a third-party proxy/CDN not associated with mp3.cc. The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged by Tier 2) obfuscate the actual file destinations. Users clicking play are routed through an unknown intermediary proxy that could serve malware, track users, or substitute content. (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='https://fine.sunproxy.net/file/NDgw...')
social engineering
The site presents itself as a legitimate free MP3 download service, mimicking the trusted MP3.cc brand on an unrelated hydr0.org subdomain. The subdomain name (arianna-feat-pitbull-sexy-people.hydr0.org) is crafted to match popular search queries, luring users searching for specific music content into visiting an impersonation site that routes downloads through an uncontrolled proxy. (location: metadata.json — domain: arianna-feat-pitbull-sexy-people.hydr0.org; page.html:5)
curl https://api.brin.sh/domain/arianna-feat-pitbull-sexy-people.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
arianna-feat-pitbull-sexy-people.hydr0.org currently scores 42/100 with a suspicious verdict and low 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.