context safety score
A score of 47/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
brand impersonation
The page is served from 'essay-feat-ida-dillan.hydr0.org' but fully impersonates MP3.cc: the title reads 'MP3.cc', the logo links to mp3.cc, the canonical tag points to mp3.cc, all navigation and footer links reference mp3.cc, and even the copyright notice states '© 2017–2026 MP3.cc'. The serving domain has no affiliation with mp3.cc, making this an unauthorized mirror/clone impersonating the legitimate brand. (location: page.html:5,9,33,609-614 — <title>, canonical href, logo href, footer)
malicious redirect
The page is hosted on 'essay-feat-ida-dillan.hydr0.org' (a subdomain of hydr0.org) but serves content styled as mp3.cc. The pre-scan context flags 1 redirect, consistent with a traffic-hijacking setup where users searching for MP3.cc or the artist content land on a third-party domain instead of the legitimate site. (location: metadata.json — url: essay-feat-ida-dillan.hydr0.org; .brin-context.md — Redirects: 1)
hidden content
All 20 audio stream URLs are routed through 'fine.sunproxy.net' with base64-encoded path segments (e.g. 'YVlGMWFTTXN3M0VjVThH...') that decode to encrypted/obfuscated internal keys. The true destination of each audio request is concealed behind this proxy layer, preventing users or agents from verifying the actual file source. The pre-scan flagged 12 suspicious base64 blobs consistent with this pattern. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 — data-url attributes)
social engineering
The sidebar contains a link to 'looz.net' (an unrelated external radio site) styled with the CSS class 'z__important' and opened in a new tab (target='_blank'). The special CSS class suggests the site operator is deliberately promoting this external destination with elevated visual priority, potentially driving unsolicited traffic to a third-party site without clear user consent. (location: page.html:204 — <a href='https://looz.net/' class='z__important no-ajax' target='_blank'>)
curl https://api.brin.sh/domain/essay-feat-ida-dillan.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
essay-feat-ida-dillan.hydr0.org currently scores 47/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.