context safety score
A score of 42/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 drake-big-rings.hydr0.org but fully impersonates mp3.cc: the HTML title reads 'MP3.cc', the canonical link points to https://mp3.cc/t/3790009993-drake-big-rings/, the footer copyright states '© 2017 – 2026 MP3.cc', and all CSS/JS assets are loaded directly from mp3.cc. Users are presented with what appears to be the legitimate mp3.cc service while actually on a third-party domain. (location: page.html:5 (title), page.html:9 (canonical), page.html:18-19 (assets), page.html:633 (copyright))
malicious redirect
The site operates as an unauthorized mirror/clone of mp3.cc hosted on hydr0.org. The Tier 2 scan flagged 1 redirect. All user interactions (downloads, navigation) redirect to mp3.cc, but the initial landing occurs on a separate domain outside mp3.cc's control, enabling traffic interception, ad injection, or future payload delivery without the user's knowledge. (location: metadata.json (domain: drake-big-rings.hydr0.org), page.html:9 (canonical redirect to mp3.cc))
hidden content
The page includes a 'noarchive' robots meta tag which prevents web archives and crawlers from caching or indexing the page. This is a common technique used by impersonation and piracy sites to avoid detection, preserve the ability to change content without a historical record, and evade blocklist indexing. (location: page.html:8 (<meta name="robots" content="noarchive">))
obfuscated code
All 21 audio file URLs are served via fine.sunproxy.net with base64-encoded path parameters that decode to further encrypted binary blobs rather than plaintext file paths. This obfuscation hides the actual audio source endpoints from static analysis and prevents direct linking, while routing all media traffic through the third-party sunproxy.net infrastructure. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608 (data-url attributes))
social engineering
A link to the external site looz.net is embedded in the genre navigation sidebar with the class 'z__important' and presented visually alongside legitimate genre links (Pop, Dance, Rap, etc.) with the label 'Online Radio'. This disguises an off-domain external link as an internal navigation item, potentially directing users to an unrelated third-party site without clear disclosure. (location: page.html:204 (<a href="https://looz.net/" class="z__important no-ajax" target="_blank">))
curl https://api.brin.sh/domain/drake-big-rings.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
drake-big-rings.hydr0.org currently scores 42/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.