context safety score
A score of 27/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 domain uses 'celina-dion' (misspelling of 'Céline Dion') as a keyword-stuffed subdomain on muzce.com to impersonate the celebrity artist. Dozens of track listings deliberately use misspelled artist names (Celion Dion, Celin Dion, Selin Dion, Selen Dion, Silin Dion, Ciline Dion, Celein Dion, Celline Dion, Cline Dion, seline dion, Celina Dion) to capture search traffic for the real artist Céline Dion via typosquatting and SEO keyword abuse. (location: domain: celina-dion-the-power-of-love.muzce.com; page.html lines 267-892 (data-artist attributes); page-text.txt lines 199-694)
social engineering
The site offers free MP3 downloads of copyrighted Céline Dion tracks ('бесплатно и без регистрации' — free and without registration) to lure users into visiting the site and executing third-party scripts. The free music offer is a social engineering lure to drive traffic and expose users to tracking and data-collection scripts. (location: page.html line 183; page-text.txt line 139)
hidden content
Track subtitle metadata contains embedded VK.com URL reference: 'The Power Of Love ↪ vk.com/retroremixes' — a deceptive cross-promotional link embedded invisibly within song track metadata to redirect users to a third-party social network. This matches the 1 deceptive link flagged by Tier 2 heuristics. (location: page.html lines 1436-1444; page-text.txt line 1010)
obfuscated code
All 100+ MP3 track URLs use long URL-safe base64-encoded token strings (e.g., 'muzce.com/file/DHghUsgVQu2y_uz46wAntJa_LKJOTfad03Hp...') to obscure the actual file paths. These 12+ suspicious base64 blobs flagged by Tier 2 are URL tokens that hide the real resource identifiers, preventing direct analysis of the served files. The actual content of served MP3 files cannot be verified. (location: page.html lines 187, 200, 213, 226, 239 etc. (all data-track attributes))
hidden content
Third-party script loaded from muzce.39o.ru (a different .ru TLD domain, not muzce.com) with tracking parameters: 'https://muzce.39o.ru/muzce.yan?u=eZWL&pt1=muzce.com&pt2=510&pt3=php'. This script is loaded from an unverified external domain with query parameters suggesting user/session tracking. The hosting reputation is listed as Unknown. (location: page.html line 1514)
hidden content
Third-party script from ru.viadata.store loaded with a session ID parameter: 'https://ru.viadata.store/v2/comm_min.js?sid=109170'. This is an unknown commercial script from a .store TLD domain that may perform data collection, behavioral tracking, or ad injection. The domain has no established reputation context. (location: page.html line 1534)
hidden content
LiveInternet counter script in the footer exfiltrates full page URL, document referrer, page title, and screen dimensions to counter.yadro.ru on every page load: escape(d.referrer), escape(d.URL), d.title.substring(0,150), screen dimensions. While LiveInternet is a known CIS web analytics service, this constitutes systematic browsing data collection sent to a third-party Russian analytics server. (location: page.html lines 1502-1506; page-text.txt lines 1057-1061)
hidden content
Yandex Metrika initialized with webvisor:true, enabling full session recording (mouse movements, clicks, scroll behavior, and potentially form input). Combined with unknown hosting reputation and third-party scripts of unclear provenance, this represents an elevated data-collection posture beyond standard analytics. (location: page.html lines 22-27)
curl https://api.brin.sh/domain/celina-dion-the-power-of-love.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
celina-dion-the-power-of-love.muzce.com currently scores 27/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.