context safety score
A score of 62/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The domain flower-girl.hydr0.org serves content that is a full mirror/proxy of mp3.cc (a third-party music download site). The canonical URL points to https://mp3.cc/t/3045413964-flower-girl/ and all resources (CSS, JS, images) load from mp3.cc. The subdomain acts as a redirect/proxy layer, routing users to content hosted on a different domain than what was requested. The brin-context confirms 1 redirect was detected. (location: page.html:9 - canonical href, page.html:18-19 - external resource loads from mp3.cc)
brand impersonation
The page hosted at flower-girl.hydr0.org fully impersonates the MP3.cc brand: the page title reads 'Flower Girl | Download mp3 free, listen music online - MP3.cc', the logo and branding display 'MP3.cc', and all content mirrors mp3.cc. The actual serving domain (hydr0.org subdomain) is completely obscured from the user, who would believe they are on MP3.cc. (location: page.html:5 - title tag, page.html:11 - og:site_name, page.html:33-36 - logo link pointing to mp3.cc, page.html:671 - footer copyright '© 2017 – 2026 MP3.cc')
malicious redirect
All MP3 audio file download/play links route through fine.sunproxy.net, a third-party proxy/CDN domain not affiliated with mp3.cc or hydr0.org. The data-url attributes contain long base64-encoded path segments (12 suspicious base64 blobs detected in pre-scan) pointing to fine.sunproxy.net/file/. This intermediary could log requests, inject content, or redirect downloads to malicious payloads. (location: page.html:228 - data-url https://fine.sunproxy.net/file/YVlGM... (and all subsequent playlist items))
social engineering
The page presents itself as a legitimate free MP3 download service (MP3.cc) while actually operating from a different domain (flower-girl.hydr0.org). Users searching for 'flower girl' music are lured to this proxy site, which may serve as a traffic interception layer. The 'Online Radio' sidebar link points to looz.net (external domain), potentially luring users off-site. (location: page.html:204 - looz.net external link with target=_blank, page.html:671 - footer contact hydrofm@yandex.com (Russian email provider))
curl https://api.brin.sh/domain/flower-girl.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
flower-girl.hydr0.org currently scores 62/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.