context safety score
A score of 46/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
brand impersonation
The site presents itself as 'YouTube Video Downloader | YTDown' and extensively uses YouTube's brand identity and service name to attract users seeking official YouTube functionality. The domain ytdown.to is unaffiliated with YouTube/Google, yet the entire site is built around YouTube's brand to drive traffic and trust. The footer disclaimer ('This service is not affiliated with YouTube') is buried and does not mitigate the brand exploitation in titles, meta tags, and marketing copy. (location: page.html:7-8, page.html:355, page.html:634)
malicious redirect
The landing page at https://ytdown.to immediately redirects all canonical and hreflang links to https://app.ytdown.to/en11/ — a subdomain with a non-standard path pattern ('/en11/'). The canonical URL in the HTML does not match the scanned domain, indicating the root domain silently redirects visitors to the app subdomain. This subdomain-based redirect pattern is commonly used to separate tracking/ad revenue infrastructure from the branded domain. (location: page.html:10-36 (canonical and hreflang tags pointing to app.ytdown.to/en11/))
social engineering
The site uses urgency and trust-building language ('entirely safe to use', 'We value user privacy and security', 'you do not have to worry about data security or malware') in the FAQ section to preemptively neutralize user security concerns and encourage downloading. This is a classic social engineering pattern used on potentially unwanted software distribution sites to override user caution. (location: page.html:556-558, page-text.txt:491-494)
hidden content
Third-party ad scripts are loaded from the domain //aqle3.com (aqle3.com/btag.min.js) using protocol-relative URLs with no integrity/subresource integrity (SRI) checks. Two separate ad zones are injected (zone 10541578 and zone 10571638). The aqle3.com domain is a known ad network associated with aggressive/intrusive advertising including potential malvertising. These scripts execute with full page access and can serve arbitrary content to users. (location: page.html:449 (data-zone=10541578), page.html:504 (data-zone=10571638))
social engineering
The site's main.js script is loaded with numerous data attributes that control UI strings and behavior (data-agreeing-terms, data-maintenance-mode, data-cooldown, etc.), meaning the server-side application controls user-facing consent and warning language dynamically. The string 'By downloading, you are agreeing to our terms and conditions' is injected via script attribute rather than presented as a clear opt-in, obscuring legal consent from users. (location: page.html:676 (main.js script tag data attributes))
curl https://api.brin.sh/domain/ytdown.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
ytdown.to currently scores 46/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.