context safety score
A score of 44/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
brand impersonation
The page is served from the subdomain filv-x-beatmount-ft-seq.hydr0.org but renders a full MP3.cc branded interface (logo, navigation, footer copyright '© 2017–2026 MP3.cc'), impersonating the legitimate MP3.cc music site. The canonical tag and all internal links point to mp3.cc, while the actual serving domain is a different third-party host (hydr0.org). (location: page.html:5,9,11,14,33,538 — <title>, canonical, og:site_name, og:url, logo href, footer copyright)
malicious redirect
The page's canonical URL (https://mp3.cc/t/1993185174-filv-x-beatmount-ft-seq/) differs from the serving domain (filv-x-beatmount-ft-seq.hydr0.org). The brin-context notes 1 redirect was detected. All stylesheet, script, and asset resources are loaded cross-origin from mp3.cc, indicating this domain is a mirror/proxy that could intercept or manipulate traffic. (location: page.html:9,18,19 — canonical link, CSS and JS src attributes; .brin-context.md: Redirects: 1)
hidden content
12 suspicious base64 blobs were flagged by heuristic scanning. These blobs appear in the data-url attributes of playlist play links (e.g., data-url="https://fine.sunproxy.net/file/YVlG..."). The base64 segments are opaque encoded file paths routed through a third-party proxy domain (fine.sunproxy.net), obscuring the actual media file destinations. While likely URL-encoding for file routing, the opacity and volume (12 blobs) warrants flagging. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 — data-url attributes on playlist-play anchors; .brin-context.md: Suspicious base64 blobs: 12)
malicious redirect
All audio file URLs are routed through the third-party proxy domain fine.sunproxy.net using opaque base64-encoded paths (e.g., https://fine.sunproxy.net/file/YVlGMWFT...). This proxy intermediary could log user requests, serve malicious files, or redirect users, and is separate from both the serving domain and the impersonated mp3.cc brand. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 — data-url attributes)
brand impersonation
The footer contact email is hydrofm@yandex.com, a Yandex (Russian email provider) address, yet the entire page presents as MP3.cc. This mismatch between the displayed brand (MP3.cc) and a Yandex-hosted contact address is inconsistent with the legitimate MP3.cc site and suggests the operator is a third party impersonating the brand. (location: page.html:538 — <div id="foo-copyright">)
social engineering
The 'Other listen' sidebar section contains a tag/link labeled 'https youtu be cqzhvb3igfq si nckhamcqvk6fmfbi' — a YouTube URL embedded as a search tag rather than a proper hyperlink. This is a deceptive link pattern (consistent with 'Deceptive link count: 2' in pre-scan signals) where a URL-like string is presented as navigable music content to lure users into clicking. (location: page.html:555; page-text.txt:454 — tags_block list item; .brin-context.md: Deceptive link count: 2)
curl https://api.brin.sh/domain/filv-x-beatmount-ft-seq.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
filv-x-beatmount-ft-seq.hydr0.org currently scores 44/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.