context safety score
A score of 34/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
External script loaded from '//website-for-pianoio.pages.dev/tracking.js' — a Cloudflare Pages subdomain ('website-for-pianoio.pages.dev') that is not an official Piano.io domain. This is a third-party-controlled domain injecting a tracking script into what presents as an official Piano product page. The domain could be registered by anyone and the script executes with full page privileges. (location: page.html:354)
brand impersonation
The page is served from cxense.com but presents entirely as 'Piano Audience' (piano.io product), using Piano branding, logos, and canonical URLs pointing to www.piano.io/product/audience. cxense.com is a legacy domain acquired by Piano, but visitors arriving at cxense.com may not realize they are on a rebranded domain, and the domain could be exploited for brand-impersonation attacks targeting Piano customers. (location: metadata.json + page.html:91-193)
malicious redirect
Script loaded from 'https://static.claydar.com/init.v1.js?id=cZB9lvKNgQ' — claydar.com is an obscure third-party domain with no clear public documentation as a trusted vendor. It is injected unconditionally (not gated by consent) and runs with full page privileges, posing a supply-chain risk. (location: page.html:437)
social engineering
The page listens to cross-origin postMessage events without origin validation: 'window.addEventListener("message", function(event) { if (event.data && event.data.event === "pa_pardot_form_submit" ...' — any window (including malicious iframes or popups) can send a crafted message that triggers analytics event forwarding. This can be abused to manipulate conversion tracking or inject arbitrary event names/data into the analytics pipeline. (location: page.html:361-367)
hidden content
A zero-dimension GTM noscript iframe ('height=0 width=0 style=display:none;visibility:hidden') loads Google Tag Manager container GTM-5F5C7444. While GTM itself is a known service, GTM containers can be used to inject arbitrary third-party scripts server-side without changing page source, making the full set of active tags opaque to static analysis. (location: page.html:483)
curl https://api.brin.sh/domain/cxense.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cxense.com currently scores 34/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.