context safety score
A score of 48/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 (connected=false, cert_valid=false, san_match=false) on a domain styled as a CDN ('kwaiselfcdn.com'). Legitimate CDNs require valid TLS; a broken/absent certificate suggests the site may be intercepting traffic, serving content over plain HTTP to downgrade connections, or acting as a phishing front-end for a known brand (Kwai/Kuaishou). (location: metadata.json: tls block)
brand impersonation
The domain 'kwaiselfcdn.com' mimics the branding of Kwai (Kuaishou), a major Chinese short-video platform, by appending 'selfcdn' to the brand name. This pattern — brand name + infrastructure-sounding suffix — is a well-known technique to impersonate a brand's CDN or self-service portal while deceiving users and automated agents into trusting the domain. (location: metadata.json: domain=kwaiselfcdn.com)
phishing
Combination of brand impersonation (Kwai), failed TLS, and an empty page body is consistent with a phishing infrastructure host: the domain is registered and live but serves no legitimate content, suggesting it may be used selectively (e.g., targeted links, redirected traffic) rather than as a public-facing site, a common characteristic of phishing kit staging domains. (location: metadata.json, page.html (empty), page-text.txt (empty))
hidden content
The page HTML, visible text, and hidden-content extracts are all empty despite the domain being reachable enough to have WHOIS and hosting data. Absence of any rendered content may indicate content is only delivered to specific user-agents, IP ranges, or referrer conditions — a cloaking technique used to evade automated scanners. (location: page.html, page-text.txt, page-hidden.txt (all empty))
curl https://api.brin.sh/domain/kwaiselfcdn.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kwaiselfcdn.com currently scores 48/100 with a suspicious verdict and medium 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.