context safety score
A score of 61/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
social engineering
Site offers free MP3 downloads ('бесплатно и без регистрации' — free and without registration) of copyrighted music. This is a common lure tactic used to attract users to sites that may serve malicious ads or initiate unwanted downloads. (location: page.html:183, page-text.txt:139)
hidden content
LiveInternet tracking pixel is loaded via a base64-encoded 1x1 GIF placeholder (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7) and then dynamically replaced with a remote tracking URL (counter.yadro.ru) that harvests referrer, screen dimensions, color depth, page URL, and page title. This is covert user surveillance embedded invisibly in the page. (location: page.html:265-271)
social engineering
The domain 'elena-karpuk-zhuravlya.muzce.com' is a keyword-stuffed subdomain designed to rank in search results for the artist/song query, driving users to a potentially ad-monetized or malware-serving site under the guise of a music search result. (location: metadata.json, page.html:5)
hidden content
External script loaded from 'muzce.39o.ru' (a different domain from the main muzce.com site): https://muzce.39o.ru/muzce.yan?u=eZWL&pt1=muzce.com&pt2=510&pt3=php. The .39o.ru domain is suspicious — it is not the canonical muzce.com domain, uses a numeric subdomain registrar pattern, and the script filename (.yan) is obfuscated. This script runs with full DOM access and its purpose is opaque. (location: page.html:279)
hidden content
External script loaded from 'ru.viadata.store': https://ru.viadata.store/v2/comm_min.js?sid=109170. This third-party domain is unrelated to muzce.com and loads a minified/obfuscated JS file asynchronously. 'viadata.store' is a data broker/analytics domain that may perform fingerprinting or behavioral tracking without user consent. (location: page.html:299)
curl https://api.brin.sh/domain/elena-karpuk-zhuravlya.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
elena-karpuk-zhuravlya.muzce.com currently scores 61/100 with a caution 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.