context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is served from hydr0.org but contains a canonical tag pointing to mp3.cc, indicating a mirror/cloaking site that redirects search engine authority and user traffic. The served domain 'a-ap-rocky-summertime-again-feat-swedish-house-mafia.hydr0.org' is a subdomain-based SEO clone of mp3.cc, with all content, branding, and navigation pointing back to mp3.cc. This constitutes a redirect/cloaking setup used to intercept organic search traffic. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/3642370512-a-ap-rocky-summertime-again-feat-swedish-house-mafia/">)
brand impersonation
The site fully impersonates mp3.cc by cloning its complete UI, branding, logo, CSS, JS, and content while serving it from the unrelated hydr0.org domain. The page title, OG tags, footer copyright, and all navigation links reference mp3.cc. Users visiting the hydr0.org subdomain would believe they are on or affiliated with mp3.cc. (location: page.html:5,11,33,576 - title, og:site_name, logo link, footer copyright all reference MP3.cc)
malicious redirect
All 18 audio play URLs use a third-party proxy at fine.sunproxy.net with base64-obfuscated path tokens to obscure the actual file source and route audio streams through an intermediary. The filenames in the proxy paths embed '(Hydr0.org)' as a tag, indicating intentional traffic attribution through the cloaking domain. This proxy layer hides the true origin of media files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551 - data-url attributes)
hidden content
The page uses 'noarchive' robots meta directive to prevent search engine caching of the page, a common tactic used by copyright-infringing or cloaking sites to avoid persistent evidence of their content in public archives while still capturing search traffic. (location: page.html:8 - <meta name="robots" content="noarchive">)
social engineering
A link to looz.net is embedded in the genre sidebar and styled identically to legitimate genre navigation links (Pop, Dance, Rap, etc.) with the label 'Online Radio'. This disguises an external third-party site redirect as a standard site navigation option, deceiving users into clicking an off-domain link they may not recognize as external. (location: page.html:204 - <a href="https://looz.net/" class="z__important no-ajax" target="_blank">Online Radio</a>)
curl https://api.brin.sh/domain/a-ap-rocky-summertime-again-feat-swedish-house-mafia.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
a-ap-rocky-summertime-again-feat-swedish-house-mafia.hydr0.org currently scores 36/100 with a suspicious verdict and low 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.