context safety score
A score of 59/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 scanned URL august-by-taylor-swift.hydr0.org redirects to mp3.cc (canonical link points to https://mp3.cc/t/1175081936-august-by-taylor-swift/). The subdomain is a vanity/bait domain on hydr0.org used to lure users searching for Taylor Swift music, then proxying/mirroring the mp3.cc interface. The Tier 2 pre-scan confirms 1 redirect. The hydr0.org domain is used as an intermediary not disclosed to the user. (location: <link rel='canonical' href='https://mp3.cc/t/1175081936-august-by-taylor-swift/'> and all asset/form URLs pointing to mp3.cc)
brand impersonation
The site at august-by-taylor-swift.hydr0.org fully mirrors the MP3.cc brand — including logo, CSS, JS, all links, and footer copyright '© 2017–2026 MP3.cc' — without being the legitimate mp3.cc domain. The page presents itself as MP3.cc while being served from a third-party domain (hydr0.org), constituting brand impersonation of MP3.cc and unauthorized use of Taylor Swift's artist identity to attract traffic. (location: page.html: <title>, header logo, footer copyright, all href/src assets referencing mp3.cc)
social engineering
The domain name 'august-by-taylor-swift.hydr0.org' is crafted to appear as an official or artist-affiliated page for Taylor Swift's song 'August', exploiting artist brand recognition to drive traffic to an unlicensed MP3 download service. Users searching for the song are likely to trust the domain as legitimate. (location: Domain: august-by-taylor-swift.hydr0.org; page title: 'August By Taylor Swift | Download mp3 free, listen music online - MP3.cc')
malicious redirect
All audio file playback URLs resolve through 'fine.sunproxy.net', a third-party proxy/CDN not disclosed to the user. MP3 download links route through mp3.cc. Users clicking play or download are silently redirected through an undisclosed intermediary proxy (sunproxy.net) which could intercept requests, inject tracking, or serve modified files. (location: page.html lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589 — data-url attributes pointing to fine.sunproxy.net)
curl https://api.brin.sh/domain/august-by-taylor-swift.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
august-by-taylor-swift.hydr0.org currently scores 59/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.