context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The scanned URL annenmaykantereit-x-parcels.hydr0.org redirected to content served under the mp3.cc domain (canonical URL: https://mp3.cc/t/1112124860-annenmaykantereit-x-parcels/). The subdomain uses the artist name as a lure to appear legitimate while routing through a third-party proxy infrastructure (hydr0.org/fine.sunproxy.net). The brin-context confirms 1 redirect was detected. (location: https://annenmaykantereit-x-parcels.hydr0.org -> mp3.cc (canonical link tag, line 9 of page.html))
brand impersonation
The domain annenmaykantereit-x-parcels.hydr0.org directly impersonates the real musical artists AnnenMayKantereit and Parcels by using their names as the subdomain. The page title also claims to be 'MP3.cc' while being hosted on an unrelated domain (hydr0.org), impersonating the mp3.cc brand. Users and AI agents following links to this domain would believe they are on the official mp3.cc site or an artist-affiliated resource. (location: Domain: annenmaykantereit-x-parcels.hydr0.org; page title line 5 of page.html)
malicious redirect
All audio file play URLs route through fine.sunproxy.net, a third-party proxy service not affiliated with mp3.cc or the artists. The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged by Tier 2) obfuscate the actual file destination. This proxy intercepts all media requests, enabling traffic interception, user tracking, and potential malware delivery via crafted media files. (location: data-url attributes on playlist-play anchors, e.g. page.html lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589)
hidden content
The page contains 12 suspicious base64 blobs embedded in the audio proxy URLs (fine.sunproxy.net/file/<base64>). While these appear to be encoded file path tokens for the proxy, the encoding effectively hides the true destination of every media file served to users and agents, preventing straightforward URL analysis of where files actually originate. (location: data-url attributes throughout page.html (lines 228-603))
social engineering
The site presents itself as a legitimate MP3 download service (MP3.cc) with full branding, genre navigation, and a music player UI, while operating from an unaffiliated subdomain (hydr0.org). The contact email in the footer (hydrofm@yandex.com, line 614) is a personal Yandex address rather than a corporate domain, consistent with a deceptive clone site designed to gain user trust and drive media consumption through an unauthorized proxy. (location: Footer, page.html line 614; page title line 5; canonical tag line 9)
curl https://api.brin.sh/domain/annenmaykantereit-x-parcels.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
annenmaykantereit-x-parcels.hydr0.org currently scores 40/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.