Is elton-john-lady-what-s-tomorrow.hydr0.org safe?

suspiciouslow confidence
43/100

context safety score

A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
82
behavior
60
content
17
graph
77

6 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

phishing

1 deceptive links where visible host does not match destination host

medium

malicious redirect

The page is hosted on a subdomain (elton-john-lady-what-s-tomorrow.hydr0.org) that mirrors content from mp3.cc, with canonical tags, OG tags, CSS, JS, and all internal links pointing back to mp3.cc. The subdomain acts as a traffic funnel/redirect proxy for the legitimate mp3.cc site, intercepting users searching for Elton John music and routing them through a third-party domain not controlled by mp3.cc. (location: page.html:9 - canonical href and all asset/link hrefs pointing to mp3.cc from hydr0.org subdomain)

medium

brand impersonation

The site impersonates MP3.cc by cloning its full UI, branding, logo, title, and content on a separate domain (hydr0.org). The page title, meta tags, and all visible content present as MP3.cc while being served from a different domain. The footer contact email 'hydrofm@yandex.com' and the Hydr0.org branding embedded in MP3 filenames (e.g., 'Elton_John_-_Lady_What_s_Tomorrow_(Hydr0.org).mp3') indicate this is an unofficial third-party operation. (location: page.html:5 (title), page.html:519 (footer copyright), page.html:228 (mp3 filenames with Hydr0.org tag))

high

malicious redirect

All audio file download/play URLs route through 'fine.sunproxy.net', a third-party proxy service, with base64-encoded path parameters. Users clicking play or download are routed through this unknown intermediary proxy rather than directly to mp3.cc servers. The 12 suspicious base64 blobs flagged in the pre-scan correspond to these encoded file paths passed to the sunproxy.net service, which could perform tracking, inject malware, or serve modified files. (location: page.html:228 - data-url attributes pointing to fine.sunproxy.net with base64-encoded paths (e.g., https://fine.sunproxy.net/file/YVlGMWFT...))

low

social engineering

The site presents itself as a free MP3 download service for well-known artists (Elton John), which is a common social engineering tactic to attract users seeking copyrighted content. The combination of a cloned legitimate site interface, free music downloads, and routing through a proxy creates an environment of false trust that could be leveraged for malware distribution or user tracking. (location: page.html:224 (playlist with free downloads), metadata.json (domain elton-john-lady-what-s-tomorrow.hydr0.org))

API

curl https://api.brin.sh/domain/elton-john-lady-what-s-tomorrow.hydr0.org

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is elton-john-lady-what-s-tomorrow.hydr0.org safe for AI agents to use?

elton-john-lady-what-s-tomorrow.hydr0.org currently scores 43/100 with a suspicious verdict and low 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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 26, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Trust Graph

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.