context safety score
A score of 55/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
3 deceptive links where visible host does not match destination host
malicious redirect
The scanned domain arianna-ft-pitbull-sexy-peoplr.hydr0.org serves content that impersonates MP3.cc (mp3.cc), with canonical URLs, Open Graph tags, CSS, and JS all pointing back to mp3.cc. The page was reached via hydr0.org but presents itself entirely as mp3.cc, indicating a redirect/proxy arrangement that masks the true serving domain. (location: page.html:9 - canonical href, og:url, and all resource links point to https://mp3.cc/ while the actual serving domain is hydr0.org)
brand impersonation
The page fully impersonates MP3.cc (a legitimate music download site) by mirroring its branding, logo, layout, CSS, and JS. The page is hosted on hydr0.org but presents itself as MP3.cc in title, meta tags, Open Graph properties, and all internal links. The Hydr0.org watermark appears in MP3 filenames (e.g., 'Arianna_feat._Pitbull_-_Sexy_People_The_Fiat_Song_(Hydr0.org).mp3'), indicating the proxy site is re-branding/re-hosting MP3.cc content under the hydr0.org domain. (location: page.html:5 title tag, line 11 og:site_name, line 329 footer copyright)
malicious redirect
Audio file download/play links use 'fine.sunproxy.net' as a proxy intermediary rather than the canonical mp3.cc domain. The base64-encoded path segments in the data-url attributes (e.g., NDgwdkFuTUxJZ0tH...) are consistent with obfuscated file tokens routed through a third-party proxy (sunproxy.net), which could intercept user traffic or serve malicious payloads instead of legitimate MP3 files. (location: page.html:228, 247, 266, 285, 304 - data-url attributes pointing to fine.sunproxy.net)
hidden content
Five suspicious base64 blobs are present in the data-url attributes of playlist play links. These are encoded strings passed to fine.sunproxy.net/file/ endpoints. While they may be legitimate file tokens, their opaque encoding obscures the actual resource being fetched and prevents transparent inspection of the download target. (location: page.html:228, 247, 266, 285, 304 - NDgwdkFuTUxJZ0tH... base64 tokens in data-url attributes)
social engineering
The page presents itself as a free MP3 download site with familiar branding (MP3.cc) while actually operating from a different domain (hydr0.org). Users searching for music may be deceived into trusting and downloading files from an unverified third-party proxy (sunproxy.net) believing they are on the legitimate MP3.cc website. (location: page.html - overall page structure and domain mismatch between hydr0.org serving domain and mp3.cc branding)
curl https://api.brin.sh/domain/arianna-ft-pitbull-sexy-peoplr.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
arianna-ft-pitbull-sexy-peoplr.hydr0.org currently scores 55/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.