context safety score
A score of 34/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The page is served from domain dj-fortee-feat-komplexity-akhona.hydr0.org but presents itself entirely as MP3.cc, including the MP3.cc logo, branding, canonical URL pointing to mp3.cc, og:site_name set to 'MP3.cc', and footer copyright '© 2017–2026 MP3.cc'. The actual serving domain has no relationship to mp3.cc, constituting brand impersonation of the MP3.cc service. (location: page.html:5,9,11,14,33,386 — <title>, canonical, og:site_name, og:url, header logo, footer copyright)
malicious redirect
The canonical link tag and all Open Graph URL tags redirect users and crawlers to https://mp3.cc/t/1968808047-dj-fortee-feat-komplexity-akhona/, a different domain than the one serving the page. This is a deceptive redirect pattern where the page is hosted on hydr0.org but canonically points to mp3.cc, potentially used for SEO manipulation or traffic interception. (location: page.html:9 — <link rel="canonical" href="https://mp3.cc/t/1968808047-dj-fortee-feat-komplexity-akhona/">)
malicious redirect
All audio file play links use a third-party proxy domain 'fine.sunproxy.net' with base64-encoded path parameters to serve MP3 files. This routes media traffic through an intermediary proxy that could intercept, modify, or log requests. The base64-encoded tokens in the URLs obscure the actual file paths and destinations, consistent with traffic laundering or data exfiltration infrastructure. (location: page.html:228,247,266,285,304,323,342,361 — data-url attributes pointing to https://fine.sunproxy.net/file/<base64>)
obfuscated code
Eight base64-encoded blobs are embedded in the play link data-url attributes (e.g. YVlGMWFTTXN3M0VjVThHdEhvZHd2bG9QWDhzMDl6Skw4YWVUNE9ZSTVLNCtzRVptNHpVcjNteVdyRDZIRWwvTTNJR2c4Ym9iZURJUDV0UDJDcDNZT3JJdjR3azRFS2dSM0dNVEhla3hKRFk9). These are consistent with the 8 'suspicious base64 blobs' flagged in Tier 2. While they may encode signed file tokens, they obscure the actual media file paths and destination parameters, preventing transparency about where requests are routed. (location: page.html:228,247,266,285,304,323,342,361 — base64 path segments in fine.sunproxy.net URLs)
brand impersonation
The page title, metadata, and all navigation links reference and link to mp3.cc (external domain), while the contact email in the footer is 'hydrofm@yandex.com' — a Yandex email inconsistent with the MP3.cc brand being impersonated. This mixing of MP3.cc branding with a Yandex contact address suggests the page is a clone or scraped mirror operated by a third party. (location: page.html:386 — <div id="foo-copyright">© 2017 – 2026 MP3.cc<br/>hydrofm@yandex.com</div>)
social engineering
The page presents free MP3 download functionality hosted on a subdomain (hydr0.org) while visually impersonating a legitimate music service (MP3.cc). Users searching for the artist may land on this mirror site and interact with it believing it is the legitimate MP3.cc service, potentially exposing them to malicious proxied content or future credential harvesting. (location: page.html — overall page structure and branding)
curl https://api.brin.sh/domain/dj-fortee-feat-komplexity-akhona.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dj-fortee-feat-komplexity-akhona.hydr0.org currently scores 34/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.