context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The site tubidy.buzz impersonates the well-known Tubidy brand, operating on a .buzz TLD rather than any officially recognized Tubidy domain. All internal links and canonical tags redirect to www39.tubidy.buzz — a subdomain-numbered pattern (www39) characteristic of mirror/clone networks that replicate legitimate brands across many subdomains to evade takedowns. (location: page.html:6 — canonical href='https://www39.tubidy.buzz/'; metadata.json domain=tubidy.buzz)
malicious redirect
The canonical URL and all navigation, footer, and asset links redirect from the visited domain (tubidy.buzz) to www39.tubidy.buzz. This subdomain-numbered redirect pattern is commonly used in typosquatting and brand-clone networks to funnel traffic through rotating infrastructure while keeping the landing page indexed under a cleaner domain. (location: page.html:6,17,52,56,57,58,64,65,66,67 — all hrefs point to https://www39.tubidy.buzz/)
hidden content
Multiple script tags use a non-standard type attribute value ('62c36a5b143bc87ba61321df-text/javascript') instead of the standard 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation token, but it also serves to delay and conditionally execute scripts in a way that can hide behavior from static scanners. The inline scripts for Google Tag Manager and the main UI logic are both gated behind this non-standard type, meaning they only execute after Cloudflare's rocket-loader.min.js processes them. (location: page.html:458,661,662 — script type='62c36a5b143bc87ba61321df-text/javascript')
social engineering
The page explicitly claims 'Tubidy is completely safe and secure... free from malware and viruses, and we do not collect any user data' while simultaneously loading Google Tag Manager (GA4 tag G-VPZDFPTL4C) which does collect user behavioral data. This false safety assurance is designed to lower user guard and encourage downloading of files whose provenance cannot be verified, facilitating potential malware distribution via downloaded MP3/MP4 files. (location: page.html:416 — FAQ answer 'Is Tubidy MP3 Download safe to use?'; page.html:661 — Google Analytics gtag G-VPZDFPTL4C)
brand impersonation
Inflated and fabricated schema.org AggregateRating data (4.9/5 from 12,167 ratings, 5,718 reviews) is embedded as structured data to manipulate search engine rich snippets and AI agent trust assessments, falsely conveying legitimacy and popularity for what is an unofficial clone site. (location: page.html:636-659 — ld+json SoftwareApplication aggregateRating)
curl https://api.brin.sh/domain/tubidy.buzzCommon questions teams ask before deciding whether to use this domain in agent workflows.
tubidy.buzz currently scores 37/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.
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.