context safety score
A score of 58/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 page is served from subdomain 2270323920.hydr0.org but all canonical URLs, links, logos, CSS, JS, and og:url tags point to mp3.cc. The page impersonates mp3.cc while being hosted on an unrelated third-party domain (hydr0.org). All audio file download links route through fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc, which intercepts media requests and could serve malicious files or track users. (location: page.html:9 (canonical), page.html:228 (data-url attributes), metadata.json (domain: 2270323920.hydr0.org))
brand impersonation
The site at 2270323920.hydr0.org fully reproduces the MP3.cc brand identity: title tag reads 'MP3.cc', logo displays 'MP3.cc', og:site_name is 'MP3.cc', og:url is 'https://mp3.cc/', and all navigation links point to mp3.cc. This is a complete brand clone of the legitimate MP3.cc service hosted on a deceptive numeric subdomain of hydr0.org. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:14 (og:url), page.html:33-36 (logo))
malicious redirect
All MP3 audio file playback URLs route through fine.sunproxy.net rather than mp3.cc or any official CDN. The base64-encoded path segments in these URLs (12 suspicious base64 blobs flagged by Tier 2) obscure the true destination. Users clicking play are sending requests to a third-party proxy (sunproxy.net) which could perform traffic interception, inject malware into downloads, or harvest behavioral data. (location: page.html:228 (data-url: https://fine.sunproxy.net/file/NDgw...), page.html:247, page.html:266 (and all subsequent playlist items))
hidden content
The page contains an HTML comment at the very end revealing internal server timing and request metadata: '<!-- 0.010147; 1 (0.001060962677002). (US|). -->' This leaks backend processing info and a geolocation hint (US) that may assist fingerprinting or targeted serving of different content to different visitors. (location: page.html:1265)
curl https://api.brin.sh/domain/2270323920.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2270323920.hydr0.org currently scores 58/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.