context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'use-tencentclb.cloud' impersonates Tencent Cloud Load Balancer (CLB) service by incorporating 'tencentclb' in the hostname under a generic .cloud TLD. This mimics Tencent's infrastructure branding (cloud.tencent.com) to deceive users or AI agents into trusting the domain as a legitimate Tencent Cloud endpoint. (location: domain: use-tencentclb.cloud)
phishing
The domain pattern 'use-tencentclb.cloud' follows a classic phishing construction: an action verb prefix ('use-') combined with a well-known brand's service name ('tencentclb') on a non-authoritative TLD (.cloud). This is consistent with credential harvesting or service impersonation phishing infrastructure targeting Tencent Cloud users. (location: domain: use-tencentclb.cloud)
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) despite the domain being active. This is anomalous for a legitimate cloud service and may indicate the domain is used for non-HTTPS redirection, traffic interception, or serves content only over plain HTTP to avoid TLS inspection — a common technique in phishing and malicious redirect infrastructure. (location: metadata.json: tls block)
hidden content
The page returned empty HTML, page-text, and page-hidden content. A domain actively registered and resolving but serving no visible content is a strong indicator of a parked phishing domain, a conditional content server (serving malicious content only to targeted victims or specific user-agents/IPs), or infrastructure awaiting activation — all high-risk patterns. (location: page.html, page-text.txt, page-hidden.txt)
curl https://api.brin.sh/domain/use-tencentclb.cloudCommon questions teams ask before deciding whether to use this domain in agent workflows.
use-tencentclb.cloud currently scores 44/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.