context safety score
A score of 46/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
malicious redirect
The domain ellie-goulding-under-control.hydr0.org uses a subdomain designed to appear as a legitimate music search result for a specific artist/song query, but redirects or proxies content entirely from mp3.cc. The canonical URL and all resource links point to mp3.cc, meaning the actual serving domain is a front/proxy layer that intercepts the user before delivering third-party content. This redirect pattern (1 redirect noted in pre-scan) is consistent with traffic interception or SEO poisoning. (location: page.html:9 - canonical href and all internal links redirect to mp3.cc)
brand impersonation
The page at hydr0.org impersonates MP3.cc by mirroring its full branding, logo, layout, stylesheet, and JavaScript from mp3.cc CDN assets. The title, OG tags, and canonical link all claim to be MP3.cc, while the actual serving domain (ellie-goulding-under-control.hydr0.org) is entirely distinct. This constitutes brand impersonation of MP3.cc to gain user trust. (location: page.html:5,9,11,18,19 - title, canonical, og:site_name, stylesheet, and script all reference mp3.cc)
malicious redirect
All audio file playback URLs use the third-party proxy domain fine.sunproxy.net with long Base64-encoded path tokens. These 12 Base64 blobs (matching the pre-scan count of 12 suspicious base64 blobs) obfuscate the actual file locations behind an untransparent proxy. Users clicking play are routed through fine.sunproxy.net rather than the canonical mp3.cc CDN, enabling traffic interception, substitution of malicious files, or tracking. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570 - data-url attributes on playlist-play anchors)
social engineering
The site presents itself as a free MP3 download service for a specific popular artist search (Ellie Goulding - Under Control) using a keyword-stuffed subdomain to attract organic or targeted traffic. The deceptive domain name (ellie-goulding-under-control.hydr0.org) mimics a direct content-match URL to lure users into trusting the site as a legitimate music source, facilitating potential malware delivery via the audio proxy. (location: metadata.json:1 - domain ellie-goulding-under-control.hydr0.org; page.html:5 - title tag)
hidden content
The pre-scan flagged 1 deceptive link. The 'Other listen' sidebar section (page.html:612) contains a large block of auto-generated tag links including one raw YouTube URL embedded as a track title ('https youtu be cqzhvb3igfq si nckhamcqvk6fmfbi'), which is abnormal and suggests automated/injected content rather than curated music links. This could be used to drive traffic to arbitrary external URLs disguised as search terms. (location: page.html:612 - tags_block ul containing embedded YouTube URL as link text/slug)
curl https://api.brin.sh/domain/ellie-goulding-under-control.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
ellie-goulding-under-control.hydr0.org currently scores 46/100 with a suspicious 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.