context safety score
A score of 38/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
malicious redirect
The page is hosted on armin-van-buuren-a-popov.hydr0.org but presents content cloned from mp3.cc, with a canonical tag pointing to https://mp3.cc/t/2144321387-armin-van-buuren-a-popov/. All navigation, download, and resource links resolve to mp3.cc while the serving domain is a subdomain of hydr0.org — a third-party proxy/mirror site serving mp3.cc content without being mp3.cc. Media files are streamed via fine.sunproxy.net, a separate proxy domain, rather than from mp3.cc or hydr0.org directly. (location: page.html:9 (canonical), page.html:228 (data-url attributes pointing to fine.sunproxy.net))
brand impersonation
The site at armin-van-buuren-a-popov.hydr0.org fully impersonates MP3.cc: it uses the MP3.cc logo, branding, site name, CSS/JS assets loaded from mp3.cc, and presents an identical UI. Users visiting the hydr0.org subdomain would believe they are on MP3.cc. The footer even reproduces the MP3.cc copyright notice ('© 2017 – 2026 MP3.cc') while the actual serving domain is hydr0.org. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:35 (logo text), page.html:671 (footer copyright))
malicious redirect
All MP3 audio file URLs in data-url attributes route through fine.sunproxy.net, a third-party proxy not affiliated with mp3.cc. File paths are base64-encoded tokens (the 12 suspicious base64 blobs flagged in Tier 2). This proxy intercepts all audio streaming requests, enabling traffic monitoring, content substitution, or malware delivery via audio/file downloads. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 (all data-url attributes))
hidden content
The Tier 2 scan flagged 12 suspicious base64 blobs. These correspond to the base64-encoded tokens embedded in every fine.sunproxy.net file URL (e.g., NDgwdkFuTUxJZ0tH...). While these are likely proxy authentication/routing tokens, they are opaque encoded strings that obscure the true destination of file download requests and cannot be verified without decoding and resolving. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 (data-url base64 path segments))
social engineering
The site mimics a legitimate music download service (MP3.cc) to build user trust, then routes all media through a third-party proxy (fine.sunproxy.net). Users are deceived into believing they are downloading/streaming from the reputable MP3.cc platform when in reality all content flows through unverified third-party infrastructure. The deceptive link flagged in Tier 2 corresponds to the looz.net 'Online Radio' link embedded in the MP3.cc-branded sidebar, directing users off-site to an unrelated domain. (location: page.html:204 (looz.net link), page.html:228+ (all proxied media URLs))
curl https://api.brin.sh/domain/armin-van-buuren-a-popov.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
armin-van-buuren-a-popov.hydr0.org currently scores 38/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.