context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
3 deceptive links where visible host does not match destination host
brand impersonation
The page is hosted on dr-techno.hydr0.org but explicitly impersonates the legitimate MP3.cc service. The HTML title reads 'Dr Techno | Download mp3 free, listen music online - MP3.cc', og:site_name is set to 'MP3.cc', og:url points to mp3.cc, and all CSS/JS resources are loaded from the mp3.cc CDN. This is a scraped mirror site using the mp3.cc brand to deceive users into believing they are on the legitimate site. (location: page.html:5 (title tag), page.html:11 (og:site_name), page.html:14 (og:url), page.html:18-19 (external CSS/JS from mp3.cc))
malicious redirect
The page includes a canonical tag pointing to https://mp3.cc/t/639963893-dr-techno/ and the Tier 1 scan detected 1 redirect. The hydr0.org domain serves a cloned mp3.cc page that redirects/defers to the legitimate domain via canonical signals, a technique used to manipulate search engine indexing and deceive users arriving at the impersonator domain. (location: page.html:9 (canonical href), metadata.json (1 redirect detected))
obfuscated code
All 12 MP3 audio file URLs in playlist data-url attributes are base64-encoded paths pointing to the third-party proxy domain fine.sunproxy.net. The base64 encoding conceals the actual file-serving infrastructure and obscures the proxied content source, making it difficult to trace copyright-infringing file delivery. Example: data-url='https://fine.sunproxy.net/file/YVlGMWFT.../<filename>.mp3' where the path component is base64. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589, 608 (data-url attributes))
social engineering
The site operates as a deceptive mirror: users who land on dr-techno.hydr0.org are presented with a fully-branded MP3.cc interface including the logo, navigation, genre sidebar, and footer copyright '2017-2026 MP3.cc'. All visible navigation links direct users to mp3.cc, creating the illusion they are on the legitimate site while the actual serving domain is hydr0.org. The meta robots tag 'noarchive' is also set, preventing web archive services from caching the deceptive copy — a common anti-forensics technique used by scraper/mirror sites. (location: page.html:8 (robots noarchive), page.html:31-36 (mp3.cc logo/branding), page.html:633 (footer copyright MP3.cc))
hidden content
The page uses the hydr0.org domain with no visible attribution or disclosure that it is a mirror. The contact email in the footer (hydrofm@yandex.com) is associated with the hydr0.org operator rather than the impersonated mp3.cc brand, and this affiliation is not disclosed to users. Additionally, three deceptive links were flagged by the Tier 2 scan: all navigation links visually appear to lead within the current site but actually direct to the external mp3.cc domain without user awareness. (location: page.html:633 (hydrofm@yandex.com footer), .brin-context.md (deceptive link count: 3))
curl https://api.brin.sh/domain/dr-techno.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-techno.hydr0.org currently scores 45/100 with a suspicious 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.