context safety score
A score of 42/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 'capcutapi.com' mimics the brand name of CapCut (a widely-used video editing app by ByteDance) by appending 'api' to the brand name, creating a convincing fake API endpoint domain that could deceive developers, AI agents, or users into trusting it as an official CapCut service. (location: domain: capcutapi.com)
phishing
The domain impersonates CapCut's brand to potentially harvest API keys, developer credentials, or user tokens from developers who believe they are integrating with an official CapCut API. TLS is not connected and certificate is invalid, indicating the site is not operating with standard security — a common trait of phishing infrastructure. (location: domain: capcutapi.com, TLS: connected=false, cert_valid=false)
credential harvesting
A fake 'API' domain impersonating a known brand (CapCut) is a classic credential harvesting vector: developers submitting API keys, OAuth tokens, or account credentials to what they believe is a legitimate API endpoint would have those credentials captured by the attacker. (location: domain: capcutapi.com)
malicious redirect
The domain has no resolvable TLS and returned empty page content, which is consistent with a parked or dormant phishing domain that may redirect visitors to malicious destinations or activate at a later time. Hosting reputation is Unknown, further supporting this assessment. (location: domain: capcutapi.com, hosting reputation: Unknown, TLS: connected=false)
curl https://api.brin.sh/domain/capcutapi.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
capcutapi.com currently scores 42/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.