context safety score
A score of 54/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
brand impersonation
The page is served from the subdomain charlotte-cardin-the-way-we-touch.hydr0.org but fully impersonates MP3.cc, including its logo, branding, canonical URLs, CSS/JS assets, and site name in all meta tags. The actual content origin is hydr0.org, a third-party domain that mirrors and impersonates the MP3.cc brand to attract users searching for the song. (location: page.html:5,9,11,14,18,19,33)
malicious redirect
The canonical link tag redirects to https://mp3.cc/t/1660187605-charlotte-cardin-the-way-we-touch/ while the page is hosted on hydr0.org. The pre-scan context also notes 1 detected redirect. This pattern is used to manipulate search engine indexing while serving traffic through the shadow domain, and can be used to redirect users after interaction. (location: page.html:9)
malicious redirect
The MP3 playback URL routes through fine.sunproxy.net, a proxy/CDN intermediary not affiliated with MP3.cc, using a long base64-encoded path segment. This is the suspicious base64 blob flagged in Tier 2. Audio content is served through an opaque proxy that could redirect, substitute, or track the download/stream without the user's knowledge. (location: page.html:228 — data-url value: https://fine.sunproxy.net/file/NDgwdkFuTUxJZ0tHbEJUVFE0QUZzeU50Smt3cnFoanUyVFdycUE0OVNpQ1EyU0hWYzJDNTUyRFkwbWZIcCtSckNyeGxzdnI3SzUvRFp5MmlLdHFZK3E3S29uV0RRdmttQnJ1ODVGekdTOG89/...)
social engineering
The site impersonates a legitimate free MP3 download service (MP3.cc) to lure users searching for a specific song into visiting a lookalike domain (hydr0.org). The page title, metadata, and content are designed to appear identical to the real service, exploiting user trust to funnel traffic through a third-party infrastructure. (location: page.html:5 — title tag; .brin-context.md — domain: charlotte-cardin-the-way-we-touch.hydr0.org)
curl https://api.brin.sh/domain/charlotte-cardin-the-way-we-touch.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
charlotte-cardin-the-way-we-touch.hydr0.org currently scores 54/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.