Home › Use cases

What real HTTPS unlocks

Modern browsers and platforms gate their most useful features behind a secure context: A page served over trusted HTTPS. A self-signed certificate throws warnings and often disables those features outright, and you simply can't point them at a bare IP. goTLS gives every service a publicly-trusted certificate on the address you already use, so all of this just works. On your laptop, your phone, and CI.

Featured

Passkeys & WebAuthn

WebAuthn refuses to run outside a secure context, and it needs a real domain as the relying-party ID — you can't register a passkey against https://192.168.1.20 or a self-signed cert. A goTLS hostname gives you both: a genuine domain and a trusted certificate.

So you can build and test passkey registration and sign-in against your local or LAN build. Including on a real phone over Wi-Fi, with no custom CA, no warnings, and no throwaway public tunnel.

# WebAuthn needs a secure context + a real domain.
# Point your relying party at a trusted goTLS host:
https://app-192-168-1-20.gotls.de

# navigator.credentials.create()/get() now work —
# on desktop and on a phone on the same network.

More things that need real HTTPS

PWAs & service workers

Service workers, install prompts, background sync and push notifications all require HTTPS. Install and test your PWA on a real phone over the LAN with a certificate the phone actually trusts.

requires HTTPS

Camera, mic & geolocation

Powerful browser APIs like getUserMedia, geolocation, the Clipboard API, Web Bluetooth and USB are secure-context only. On plain HTTP they're silently unavailable. On a goTLS host they light up.

secure context only

OAuth callbacks & webhooks

Most identity providers reject http:// redirect URIs and many webhook senders require TLS. Register a trusted https://…gotls.de callback and test the real flow locally.

https redirect URI

IoT & MQTTS fleets

Point a whole fleet at broker.10-0-0-5.gotls.de and every device gets a trusted MQTTS connection. No root CA to bring onto each device, and the broker's key never leaves the signer.

trusted on every device

Native mobile app dev

iOS App Transport Security and Android's cleartext policy expect trusted TLS. Point your app at an https://…gotls.de LAN URL and skip the ATS exceptions and debug-cert hacks.

ATS / cleartext friendly

CI & ephemeral envs

Bring a service up in a pipeline and hit it over trusted HTTPS for integration and end-to-end tests. No cert generation, no trust-store surgery on the runner, no --insecure flags.

no cert wrangling

Homelab & self-hosted

Reach your NAS, dashboards and self-hosted apps at https://nas-10-0-0-2.gotls.de with a green padlock on every device — no per-device CA install, no more "your connection is not private".

green padlock everywhere

Team demos & sharing

Share a dev-server URL with a teammate on the same network and their browser trusts it instantly. A clean HTTPS link for a demo, a review, or a quick "does this repro on your machine?".

no warnings for anyone

Get a trusted URL in one command

Run the keyless proxy in front of your service, then open the magic URL. No account, no certificate to install, no key on your box.

Build my config → Download the proxy Get started