context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
hidden content
Multiple HTML comments containing only '[' and ']' bracket characters found throughout the page, consistent with Vue.js/Nuxt SSR teleport markers. While these are framework artifacts, they represent non-visible markup that could obscure content from human review. Total of ~110 such comment nodes present. (location: page-hidden.txt lines 4-111, page.html HTML comments)
hidden content
Internal CMS preview origin 'https://cms.devcb.in' exposed in the client-side window.__NUXT__.config JavaScript block, revealing a non-public staging/development domain that could be targeted for reconnaissance or SSRF. (location: page.html, window.__NUXT__.config: cmsPreviewOrigin field)
hidden content
Multiple API keys and tokens exposed in plaintext within client-side JavaScript (window.__NUXT__.config): Contentful CDA access token ('U-NzRsrBNstwLZ9uYBEZcINmitwfL8sAMNkPnJFx0No'), Google Sheets API key ('AIzaSyBFpNLJB1M3LOyXdiZQACQnkdJjY6jjHQU'), Swiftype search engine key ('6MUYxPLDeSfPowA2zmwE'), and Chargebee publishable key ('test_eQ8cdPrlb5ZDnntOFcnoq0sZnDDksyzBO'). These are accessible to any visitor or automated agent parsing the page. (location: page.html, inline <script> block: window.__NUXT__.config.public)
malicious redirect
Login dropdown includes a link to 'https://ar.numberz.in/login/' for the 'Receivables' product login, and 'https://app.brightback.com/company/sign-in' for Retention. These are third-party domains not under the chargebee.com domain. While likely legitimate acquired/integrated products, they represent cross-domain login redirects that could confuse users about where their credentials are being submitted. (location: page.html, rc-login section: href='https://ar.numberz.in/login/' and href='https://app.brightback.com/company/sign-in')
hidden content
Third-party script 'https://static.claydar.com/init.v1.js?id=cemDtXpId3' loaded from an external domain (claydar.com) not under chargebee.com control. This script executes with full page access and its behavior cannot be verified from static analysis alone. (location: page.html, <script src='https://static.claydar.com/init.v1.js?id=cemDtXpId3' defer>)
curl https://api.brin.sh/domain/chargebee.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
chargebee.com currently scores 40/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.