context safety score
A score of 50/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
brand impersonation
The page is served from aitch-luciano.hydr0.org but fully impersonates the legitimate MP3.cc service, copying its title ('Aitch Luciano | Download mp3 free, listen music online - MP3.cc'), logo, CSS/JS assets from mp3.cc, og:site_name, canonical URL, footer copyright ('© 2017–2026 MP3.cc'), and all navigation links. The actual operator contact is hydrofm@yandex.com, inconsistent with the impersonated brand. (location: page.html:5, page.html:9-14, page.html:18-19, page.html:614)
malicious redirect
The canonical tag and og:url both declare the page's authoritative URL as https://mp3.cc/t/4289457974-aitch-luciano/ (the real MP3.cc domain), while the page is actually served from hydr0.org. This misdirects crawlers and agents about the true origin of the content, consistent with the 1 redirect flagged in pre-scan context. (location: page.html:9 (canonical), page.html:14 (og:url), .brin-context.md: Redirects: 1)
obfuscated code
All 19 playlist audio play buttons use data-url attributes containing long base64-encoded strings (12 flagged by scanner) pointing to fine.sunproxy.net. These encode opaque signed/encrypted token paths that obscure the actual MP3 file origins and route all audio through a third-party proxy, evading copyright detection and enabling traffic interception or user tracking. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570 (data-url attributes))
social engineering
A sidebar genre link to https://looz.net/ (an unrelated third-party radio site) is embedded among legitimate genre navigation links using the CSS class 'z__important', presenting an off-brand external site as a peer navigation option to drive traffic to a separate property without clear disclosure. (location: page.html:204-215)
curl https://api.brin.sh/domain/aitch-luciano.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
aitch-luciano.hydr0.org currently scores 50/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.