context safety score
A score of 44/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
social engineering
The site offers free MP3 320kbps downloads of copyrighted commercial music (e.g., Katy Perry feat. Juicy J 'Dark Horse', multiple tracks) without authorization, advertised as 'free and without registration' ('бесплатно и без регистрации'). This is a social engineering lure to attract users to an unauthorized piracy platform, increasing exposure to ad-based or drive-by threats. (location: page.html:183, page.html:57-63)
malicious redirect
A third-party script is loaded from 'https://muzce.39o.ru/muzce.yan?u=eZWL&pt1=muzce.com&pt2=510&pt3=php' — this is a subdomain of '39o.ru', not the main 'muzce.com' domain. The domain '39o.ru' is unknown/unvetted and different from the site's primary domain. The script is loaded with 'defer' and passes tracking parameters (u, pt1, pt2, pt3). This off-brand external script loader presents a supply-chain/malicious redirect risk. (location: page.html:1514)
hidden content
The Yandex Metrika noscript tracking pixel uses 'position:absolute; left:-9999px;' to position the image off-screen, effectively hiding it from visible content. While standard for analytics, this constitutes a hidden content technique. (location: page.html:28)
hidden content
The LiveInternet counter image is initialized with a 1x1 transparent GIF data URI ('data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7') and its src is replaced at runtime via JavaScript to load a tracking beacon from 'https://counter.yadro.ru/hit', which collects referrer, screen dimensions, color depth, page URL, and page title — a covert data exfiltration pattern via a hidden tracker. (location: page.html:1499-1506)
social engineering
The 'currently listening' sidebar ('Сейчас слушают') lists real-time popular searches to create social proof and urgency, encouraging deeper engagement with the piracy platform. This is a standard dark-pattern engagement technique. (location: page.html:71-173)
brand impersonation
The subdomain 'dark-sound.muzce.com' is structured as a search-result page for 'Dark sound', with a canonical URL and structured data (schema.org ItemList/MusicRecording) referencing copyrighted artists and tracks (Katy Perry, Epidemic Sound, etc.), impersonating a legitimate music search/streaming service to mislead users about the legitimacy and authorization of the content. (location: page.html:5-7, metadata.json)
curl https://api.brin.sh/domain/dark-sound.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dark-sound.muzce.com 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.