context safety score
A score of 58/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 page is hosted on a subdomain of hydr0.org (acha-septriasa-ft-irwansyah.hydr0.org) but all canonical links, CSS, JS, images, and navigation links point to mp3.cc. The canonical tag explicitly redirects search engines and agents to https://mp3.cc/t/2282075458-acha-septriasa-ft-irwansyah/. This is a domain-squatting mirror pattern where the hydr0.org domain serves cloned mp3.cc content to intercept traffic and redirect users off the original domain. (location: page.html:9 - canonical href and all resource links point to mp3.cc while served from hydr0.org subdomain)
brand impersonation
The site at hydr0.org fully impersonates the MP3.cc brand: it uses the MP3.cc logo, title, branding, stylesheet, JavaScript, and content layout identical to mp3.cc. The page title reads 'MP3.cc', the footer shows '© 2017 – 2026 MP3.cc', and all UI elements reference mp3.cc. The actual serving domain (hydr0.org) is unrelated to MP3.cc, constituting clear brand impersonation of a legitimate music service. (location: page.html:5,34-36,557 - title, logo, footer all display MP3.cc branding while served from hydr0.org)
malicious redirect
All audio file download/play URLs route through fine.sunproxy.net, a third-party proxy domain unrelated to either hydr0.org or mp3.cc. The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged by Tier 2) obfuscate the true destination of audio file requests, routing all media traffic through an unknown intermediary proxy that could intercept connections, log user activity, or serve malicious payloads instead of audio files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532 - all data-url attributes point to fine.sunproxy.net/file/ with base64-encoded paths)
hidden content
The page HTML contains an HTML comment with a server performance metric: '<!-- 0.690069; 1 (0.00069189071655273). (US|). -->' appended after the closing </html> tag. While this appears to be a benign server-side timing comment, it leaks server infrastructure information including response time and region code (US). (location: page.html:638 - comment after closing </html> tag)
curl https://api.brin.sh/domain/acha-septriasa-ft-irwansyah.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
acha-septriasa-ft-irwansyah.hydr0.org currently scores 58/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.