Expired50% confidenceFactExact time
TLS encryption is terminated and re-established at each hop, meaning relay platforms themselves can still see plaintext data.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
7/2/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 9/30/2026(expired)
Sources
API Aggregation Proxy Platforms: Call All Major AI Models Through a Single Interface
bilibili无游戏知心6/24/2026
Related Claims
UnverifiedTLS encryption only protects transmission security between the user and the relay server; relay server operators can technically log all of a user's conversation content.77% similarVerifiedTLS encryption, on which HTTPS relies, only protects the transmission channel between two communication endpoints; in a relay proxy model, the relay server is the TLS session endpoint and can read plaintext request content after completing TLS termination.76% similarUnverifiedCompared to TLS 1.2, TLS 1.3 simplifies the handshake process (reducing from 2-RTT to 1-RTT), removes insecure cipher suites, and enables forward secrecy by default75% similarUnverifiedAn HTTPS man-in-the-middle proxy tool completes the TLS handshake with the app using its own certificate, while simultaneously establishing a separate TLS connection with the server using the server's real certificate, enabling decryption and re-encryption of encrypted traffic.72% similarUnverifiedCommon implementation schemes for end-to-end encryption include X25519-based key exchange combined with AES-256-GCM symmetric encryption; for LAN direct-connect scenarios, TLS 1.3 is already sufficient to meet transport security requirements.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/41012API
curl https://kongchang.com/api/v1/knowledge/claims/41012MCP
get_claim(id=41012)