Automatic SSL
HTTPS on every link
HTTPS on every link, including custom domains — no configuration needed.
What it does
Every link created on Nimble Links is served over HTTPS — whether it's on the default nimble.li domain or on your own custom domain. For custom domains, SSL certificates are issued and renewed automatically when you connect the domain. There's nothing to configure.
Custom domains
When you add a custom domain and point its DNS to Nimble Links, an SSL certificate is provisioned automatically. You don't need to generate certificates, upload key files, or set up DNS validation records. The certificate renews on its own before it expires.
Your custom domains
This means your branded links (like go.acme.co/promo) are served over HTTPS from the moment the domain is active — with the padlock icon in the browser and no security warnings.
Default domain
Links on nimble.li are always served over HTTPS. There's nothing to enable — it's the default for every link you create.
Why this matters
Browsers display a "Not Secure" warning for pages served over HTTP. If someone clicks a link that loads over HTTP — even if it redirects to a secure destination — they may see a warning before the redirect happens. HTTPS on your short links prevents this.
Some platforms (including email clients and messaging apps) also treat HTTPS links differently than HTTP links when generating previews. HTTPS links are more likely to show rich previews with titles and images.
What's covered
- nimble.li — HTTPS by default
- Custom domains — SSL certificates issued and renewed automatically
- Link-in-bio, music, and podcast pages — Served over HTTPS with valid certificates
- API endpoints — All API traffic is encrypted