context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for cqpay.io. A payment-themed domain that does not serve a valid HTTPS connection is strongly indicative of a deceptive or non-functional site that may redirect users or harvest credentials without a secure channel. (location: metadata.json: tls block)
credential harvesting
Domain cqpay.io presents as a payment platform ('pay' in domain name) but has no functioning TLS certificate and WHOIS privacy is fully redacted. This combination is a strong indicator of a credential harvesting operation targeting payment or financial account credentials. (location: metadata.json: domain, tls, whois blocks)
brand impersonation
The domain name 'cqpay.io' uses a payment-adjacent naming convention ('pay') under a non-standard TLD (.io) with WHOIS privacy redacted and unknown hosting reputation, consistent with brand impersonation of a legitimate payment processor or financial service. (location: metadata.json: domain, hosting)
phishing
Site cqpay.io combines a payment-themed domain, failed TLS (no valid certificate), fully redacted WHOIS, and unknown hosting reputation with completely empty page content — consistent with a phishing site that may be dormant, cloaking content from crawlers, or serving malicious content only to targeted victims. (location: metadata.json, page.html, page-text.txt (empty content))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the domain being resolvable enough for metadata collection. This absence of content is consistent with active cloaking — serving content only to human browsers or targeted users while presenting nothing to scanners and bots. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/cqpay.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
cqpay.io currently scores 36/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.