HTTPS on localhost.
One checkbox.

Custom domains like myapp.test with auto-generated trusted certificates. No mkcert. No openssl commands. No browser warnings.

Some features don't work without HTTPS. Secure cookies, service workers, WebAuthn, certain OAuth flows — they all demand a secure context. In production, your cloud provider handles it. In development, you're on your own.

Donk generates a local Certificate Authority, installs it in the Windows trust store, and issues certificates for any domain you configure. Check the "Enable SSL" box. Your server is now available on https://myapp.test with a green padlock. The certificate is trusted — no browser warnings, no "proceed anyway" clicks.

  • One checkbox to enable HTTPS — no config files, no CLI commands
  • Custom .test domains — myapp.test, api.myapp.test, anything
  • Auto-generated local CA installed in the Windows trust store
  • Green padlock in every browser — Chrome, Firefox, Edge all trust it
  • Wildcard certificates for subdomain routing — *.myapp.test
  • Caddy reverse proxy handles the HTTPS termination — your app sees plain HTTP
  • Works across LAN — your phone trusts it too after one CA install
🎬

Video: 20–30 seconds. Enabling SSL on a server, seeing the green padlock, opening on a phone.

Download Donk

Windows 10/11 · ~100 MB · No dependencies

Download for Windows