context safety score
A score of 42/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 26-28hz-argy-baset.hydr0.org but fully impersonates MP3.cc by cloning its branding, logo, CSS, JS, canonical URL, og:site_name, and footer copyright. The actual serving domain is a hydr0.org subdomain, not mp3.cc. (location: page.html:5-14, page.html:614)
malicious redirect
The canonical link tag redirects to https://mp3.cc/t/443401874-26-28hz-argy-baset/, routing users from the spoofed hydr0.org subdomain to the legitimate mp3.cc domain. This mirrors the 1 redirect flagged in Tier 2 analysis and may be used for SEO abuse or traffic laundering. (location: page.html:9)
malicious redirect
All 20 audio file play URLs use data-url attributes pointing to https://fine.sunproxy.net/file/... — a third-party proxy domain not affiliated with the displayed MP3.cc brand. These 12+ base64-encoded proxy URLs route media requests through an unverified intermediary (sunproxy.net), matching the 12 suspicious base64 blobs flagged in Tier 2. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589)
social engineering
The 'Online Radio' navigation link (styled identically to genre navigation items) redirects to https://looz.net/ — an entirely different external site embedded in the MP3.cc-impersonating interface without disclosure, potentially used to drive traffic to affiliated properties under false pretenses. (location: page.html:204-215)
brand impersonation
The footer displays 'hydrofm@yandex.com' as the contact email under the MP3.cc copyright notice. A legitimate MP3.cc site would use an @mp3.cc address. This inconsistency indicates the operator is not affiliated with MP3.cc and is using a personal Yandex email, further confirming the impersonation. (location: page.html:614)
curl https://api.brin.sh/domain/26-28hz-argy-baset.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
26-28hz-argy-baset.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.