context safety score
A score of 35/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
cloaking
Page loads content in transparent or zero-size iframe overlay
obfuscated code
Ad injection script at tbadverts.com uses String.fromCharCode(38) to obfuscate the '&' character in query string construction, reads and parses document.cookie inline, and dynamically appends script tags. This pattern obscures the true URL parameters being sent and is characteristic of obfuscated ad/tracking code. (location: page.html:156, 228, 2920, 2959, 2961, 2963)
obfuscated code
Third-party ad script loaded from https://js.pmx.bet (a gambling/betting domain) using a dynamic script injection pattern with CDATA wrapping and parent frame traversal. The domain 'pmx.bet' is a betting network; injecting scripts from this domain into a music site raises concerns about malicious ad redirection or malvertising. (location: page.html:114-129)
malicious redirect
Script loaded from https://js.pmx.bet — a known adult/gambling ad network domain — is injected dynamically and attempts to traverse parent frames (parent.document.getElementsByTagName). This can facilitate cross-frame ad injection or redirect users to gambling/inappropriate content from a music download site, especially on mobile. (location: page.html:119-126)
hidden content
Multiple ad placements (AADIV27, AADIV28, AADIV32, AADIV9, AADIV33) are loaded via dynamically injected scripts from tbadverts.com with no visible fallback content. The actual ad content is fully determined server-side at render time and is invisible in the static HTML, making it impossible to audit what is ultimately displayed to users. (location: page.html:156, 228, 2920, 2959, 2961, 2963)
obfuscated code
Cloudflare challenge script injected via hidden iframe (1x1px, position absolute, visibility hidden) at the bottom of the page. While this is standard Cloudflare Bot Management behavior, the pattern of creating a hidden iframe to inject challenge scripts can be used for fingerprinting and may be abused by threat actors mimicking the pattern. (location: page.html:2924)
hidden content
Several commented-out script tags referencing external ad/tracking domains are present: dgaf2ncy4dtan.cloudfront.net, jsc.adskeeper.com, bvtpk.com, ev.quellersolvend.com, s0-greate.net, ad.kubicserves.icu. While currently inactive (HTML comments), their presence suggests prior use of additional third-party ad networks, some of which (quellersolvend.com, kubicserves.icu) are associated with aggressive ad injection and redirects. (location: page.html:132-135, 144, 233)
curl https://api.brin.sh/domain/trendybeatz.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
trendybeatz.com currently scores 35/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.