context safety score
A score of 49/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
brand impersonation
The page is served from amin-rostami.hydr0.org but fully impersonates mp3.cc: the page title, logo, canonical URL, og:tags, CSS/JS assets, and all navigation links reference mp3.cc. This is a mirror/clone site presenting itself as the legitimate mp3.cc brand while operating from a different domain. (location: page.html:5,9,11,14,18,19,33,35 — title, canonical, og:site_name, og:url, logo href, stylesheet and script src all point to mp3.cc)
malicious redirect
All 20 MP3 stream URLs are routed through fine.sunproxy.net with base64-encoded path parameters rather than served directly. Users clicking play are redirected through an opaque third-party proxy (fine.sunproxy.net) whose trustworthiness is unknown. This proxy intercepts all media requests and could serve malicious content or track users. (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 attributes on all playlist-play anchors)
brand impersonation
The canonical link tag explicitly redirects to https://mp3.cc/t/2395204324-amin-rostami/, signaling the page is a shadow copy of an mp3.cc artist page. The .brin-context.md confirms 1 redirect was detected. The page deceives visitors into believing they are on mp3.cc when they are on a third-party subdomain. (location: page.html:9 — <link rel="canonical" href="https://mp3.cc/t/2395204324-amin-rostami/">)
social engineering
The sidebar contains an 'Online Radio' link pointing to an off-domain site (https://looz.net/) styled identically to the site's own genre navigation links, with no visual distinction. Users may be misled into thinking this is part of the mp3.cc ecosystem when it is an external off-domain destination. (location: page.html:204 — <a href="https://looz.net/" class="z__important no-ajax" target="_blank">Online Radio</a>)
hidden content
An HTML comment in the page source contains a Russian-language developer instruction ('чтобы показать #fixplayer-notification нужно добавить .js__notify для #fixplayer-lcd'). Combined with the footer contact email hydrofm@yandex.com, this indicates the site operators are Russian-speaking, consistent with the hydr0.org domain used for pirated content distribution. This is contextual rather than a direct injection threat. (location: page.html:675 — HTML comment with Russian text; page.html:633 — hydrofm@yandex.com in footer)
curl https://api.brin.sh/domain/amin-rostami.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
amin-rostami.hydr0.org currently scores 49/100 with a suspicious verdict and medium 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.