context safety score
A score of 76/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
brand impersonation
The page is served from subdomain 'your-love-by-juris-fernadrez.hydr0.org' but presents itself entirely as 'MP3.cc', using MP3.cc branding, logo, canonical URLs, og:site_name, og:url, and footer copyright. The hosting domain 'hydr0.org' (with zero replacing letter 'o') is distinct from 'mp3.cc', indicating the content is mirroring/spoofing the MP3.cc brand from an unrelated third-party domain. (location: page.html:5,9,11,14,33-35,234 — title, canonical, og tags, logo, footer)
malicious redirect
The brin-context signals 1 redirect was detected. The canonical link points to 'https://mp3.cc/t/3590852971-your-love-by-juris-fernadrez/' while the actual serving domain is 'your-love-by-juris-fernadrez.hydr0.org', suggesting traffic is being proxied or redirected through this third-party domain before potentially forwarding to the legitimate site. (location: page.html:9 — canonical href, metadata.json — url field vs canonical mismatch)
hidden content
A fatal PHP error stack trace is rendered in the page body, leaking full server-side file paths including '/var/www/oxy/data/www/hydro.fm/system/libs/mysqliExtended.php' and internal class/method names. This is information disclosure that could aid targeted attacks, and is visible in the rendered page output rather than being hidden from users. (location: page.html:249-258, page-text.txt:148-157)
curl https://api.brin.sh/domain/your-love-by-juris-fernadrez.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
your-love-by-juris-fernadrez.hydr0.org currently scores 76/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.