context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The domain artik-pres-asti.hydr0.org serves content impersonating MP3.cc (mp3.cc), with canonical URLs, CSS, JS, and all navigation links pointing to mp3.cc. The subdomain hydr0.org acts as a proxy/mirror that intercepts user traffic intended for the legitimate mp3.cc service. All audio file downloads are proxied through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. (location: page.html:9 (canonical), page.html:18-19 (external CSS/JS from mp3.cc), page.html:228 (data-url pointing to fine.sunproxy.net))
brand impersonation
The site at artik-pres-asti.hydr0.org fully impersonates MP3.cc, reproducing its logo, layout, genre navigation, playlist UI, footer copyright ('© 2017 – 2026 MP3.cc'), and contact email (hydrofm@yandex.com). Users interacting with this site believe they are on mp3.cc when they are actually on a third-party subdomain (hydr0.org) with no affiliation to the real mp3.cc brand. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:33-36 (logo), page.html:652 (footer copyright))
malicious redirect
All MP3 audio file URLs use the domain fine.sunproxy.net as a proxy layer (12 base64-encoded file paths). This routes user media requests through an uncontrolled third-party proxy that can intercept, log, or manipulate downloads. The base64-encoded path parameters (flagged as 12 suspicious blobs) obfuscate the true file destinations. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 (data-url attributes))
hidden content
The page sets 'noarchive' in the robots meta tag, preventing search engines and web archives from caching the page content. This is consistent with evasion of content archiving and security scanning, reducing the ability to track changes or document the site's impersonation behavior over time. (location: page.html:8 (meta name='robots' content='noarchive'))
social engineering
The site presents itself as a fully functional music download service (MP3.cc mirror), providing real playlist content, working play/download controls, and familiar branding to build user trust. The deceptive link (flagged in Tier 2: deceptive_link_count=1) corresponds to the sidebar link to looz.net (line 204) labeled 'Online Radio', which redirects users to an entirely different third-party site (looz.net) without clear disclosure that it leaves the apparent mp3.cc context. (location: page.html:204 (a href='https://looz.net/' class='z__important no-ajax' target='_blank'))
curl https://api.brin.sh/domain/artik-pres-asti.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
artik-pres-asti.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.