context safety score
A score of 51/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The page is served from domain 'drake-feat-quavo-travi-scott.hydr0.org' but fully impersonates MP3.cc, including its logo, branding, canonical tag pointing to 'https://mp3.cc/t/3408866513-drake-feat-quavo-travi-scott/', og:site_name 'MP3.cc', and all internal navigation links pointing to mp3.cc. This is a third-party domain cloning the MP3.cc brand to serve content under a different domain. (location: page.html:5,9,11,14,33-36)
malicious redirect
The actual serving domain is 'hydr0.org' (subdomain: drake-feat-quavo-travi-scott.hydr0.org) but the canonical link and all content reference 'mp3.cc'. The Tier 2 scan detected 1 redirect. Users navigating to this URL are served a cloned MP3.cc page from a different domain, potentially as a traffic-hijacking or SEO poisoning mechanism. (location: metadata.json (domain: drake-feat-quavo-travi-scott.hydr0.org), page.html:9)
malicious redirect
All audio file playback URLs point to 'fine.sunproxy.net', a third-party proxy domain not affiliated with mp3.cc. Audio requests are routed through this external proxy with base64-encoded tokens, obscuring the true file origin and routing user traffic through an unverified intermediary. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589)
social engineering
A sidebar link styled with class 'z__important' points to 'https://looz.net/' labeled 'Online Radio', opening in a new tab (_blank). This link is visually distinguished from other genre links and directs users off-domain to an unrelated third-party site, which may be used for traffic monetization or further redirection. (location: page.html:204-215)
curl https://api.brin.sh/domain/drake-feat-quavo-travi-scott.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
drake-feat-quavo-travi-scott.hydr0.org currently scores 51/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.