context safety score
A score of 48/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 page is served from domain findsamusic.co.za but all content, assets, canonical URL, og:url, og:site_name, and structured data claim the site is 'Tubidy' located at cutfm.co.za. The actual Tubidy service operates at tubidy.com. This site impersonates the well-known Tubidy brand using two different domains (findsamusic.co.za serving content that identifies itself as cutfm.co.za/Tubidy) to exploit brand recognition for traffic. (location: page.html:7-25, og:url=https://cutfm.co.za, canonical href=https://cutfm.co.za, page title, navbar brand)
malicious redirect
The scanned URL is https://findsamusic.co.za, but every link, asset, canonical tag, og:url, hreflang, and structured data URL points to https://cutfm.co.za. The page appears to be a doorway/redirect site that loads content from a separate domain to funnel users away from the scanned domain to cutfm.co.za, which itself impersonates Tubidy (tubidy.com). (location: page.html:25-40, canonical href, og:url, all nav hrefs, all asset srefs pointing to cutfm.co.za)
brand impersonation
Social media links on the page point to https://www.facebook.com/tubidy and https://twitter.com/tubidy — official Tubidy accounts — falsely implying this site (findsamusic.co.za / cutfm.co.za) is the authentic Tubidy service when it is not tubidy.com. (location: page.html:272-280)
social engineering
The page is styled and written to appear as the legitimate Tubidy download platform, including a detailed FAQ, structured data with the Tubidy brand name, and instructions directing users to 'visit Tubidy.com' while actually hosting the content on cutfm.co.za served via findsamusic.co.za. This is designed to build false trust and drive downloads or ad clicks. (location: page-text.txt:748-1009, page.html:862-1126)
curl https://api.brin.sh/domain/findsamusic.co.zaCommon questions teams ask before deciding whether to use this domain in agent workflows.
findsamusic.co.za currently scores 48/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.