context safety score
A score of 68/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
malicious redirect
The scanned URL (2155115302.hydr0.org) is a numeric subdomain that serves content belonging to mp3.cc, including canonical tags, all links, and assets pointing to mp3.cc. The actual domain visited differs from the brand domain presented, indicating a redirect/proxy arrangement where traffic is funnelled through an unbranded numeric host before landing on the mp3.cc content. (location: page.html:9 — <link rel="canonical" href="https://mp3.cc/">; metadata.json domain: 2155115302.hydr0.org)
brand impersonation
The page fully impersonates mp3.cc (logo, branding, canonical URL, all navigation and download links) while being served from the unrelated domain 2155115302.hydr0.org (a numeric subdomain of hydr0.org). Users and AI agents resolving the URL would encounter content that appears to be mp3.cc but is hosted on a different infrastructure. (location: page.html:5,9,11,14,33 — title, canonical, og:site_name, og:url, logo link all reference mp3.cc while served from 2155115302.hydr0.org)
malicious redirect
All MP3 play links resolve through fine.sunproxy.net rather than mp3.cc itself. sunproxy.net is a third-party proxy/CDN not mentioned in the visible branding. Every audio file is fetched via a base64-encoded token URL on this external proxy, representing 12+ suspicious base64 blobs (matching the Tier 2 signal of 12 suspicious base64 blobs) that could be used to track users, serve malicious payloads, or redirect audio requests to untrusted infrastructure. (location: page.html:228,247,266 (and all subsequent playlist-play data-url attributes) — https://fine.sunproxy.net/file/<base64>/<filename>.mp3)
hidden content
An 'Other listen' tag cloud block contains a large block of algorithmically generated search terms (artist names, song fragments, foreign-language strings) injected into the sidebar. While not hidden via CSS in the traditional sense, this content is visually de-emphasised and appears designed to manipulate search/recommendation algorithms rather than serve users, a common SEO spam or cloaking technique. (location: page.html:1199-1202 / page-text.txt:1099-1101 — <div class="sblock"><h3>Other listen</h3><ul class="tags_block">...)
curl https://api.brin.sh/domain/2155115302.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2155115302.hydr0.org currently scores 68/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.