Does DChat support HTTPS and secure WebSockets?
Yes. Chat traffic runs over HTTPS, and the realtime connection upgrades to a secure WebSocket on the same origin. Because you host it, the certificate is yours - corporate PKI, a commercial certificate, or automated issuance all work.
Must the widget be served over the same scheme as my page?
Yes. A browser blocks an insecure script on a secure page, so an HTTPS site must load the widget from an HTTPS server address. Point the embed's server URL at your https origin and the realtime connection follows automatically.
Can I terminate TLS at a reverse proxy or CDN?
That is a common deployment. Terminate at IIS, Nginx or your CDN and forward to the application. Configure your proxy to preserve the original host and scheme, and set the application's public URL to the https address your visitors use, so generated links and the widget's origin match.
What about the Windows desktop agent console?
Include the scheme in the App Site URL - type https://your-server (or http:// for a plain-HTTP test server) and the console connects accordingly. Only a bare host name falls back to the 'use secure connection' option in Options.
What other transport protections are in place?
Every response carries a strict Content-Security-Policy plus X-Content-Type-Options, X-Frame-Options, Referrer-Policy and X-Permitted-Cross-Domain-Policies. Visitor-facing endpoints are rate limited per IP, and webhooks can be HMAC-SHA256 signed so a receiver can verify they came from you.