NakedSSL is the easiest way to create 301 redirects for your naked domain — even with SSL. Check now if we can redirect your domain.
NakedSSL works with Heroku, Netlify, Vercel, AWS S3, Hasura, Google App Engine — you name it, we got. Keep your provider — NakedSSL redirects your apex domain with SSL.
Servers in the EU & the US create a better user experience and faster redirection by choosing the region closer to the majority of your users.
NakedSSL works perfectly with low-to-medium traffic websites & apps, from a few dozen to several thousand visitors per day. We are pretty sure we can scale with you.
We do not collect or store any data related to your website: we just apply an SSL 301 redirect to your domain and your visitors won't even notice the redirection on your bare domain.
No need to transfer your bare domain, change your DNS provider or configure complex settings yourself. Just add a simple DNS record and we'll add some SSL clothes to your naked domain.
Thanks to the power of Let’s Encrypt, you can now forget about provisioning servers, generating SSL certificates, installing & managing them: just a few clicks and we take care of everything.
If your domain have been in “generating ssl certificate” for longer than 24h, there is probably an issue with the configuration in your domain – most likely related to the DNS changes. We know that DNS updates can be tricky, especially if you’re not tech savvy, so the first thing you have to check is that your naked domain only has ONE DNS A (IPv4) or AAAA (IPv6) Record(s) pointing to the IP that NakedSSL gave you. You can easily do this by doing a DNS Lookup here, where you should type your domain. The result should be something similar to this for DNS A Records. For security reasons, LetsEncrypt won’t issue a certificate if you have multiple IPs as DNS A/AAAA Records, so if you see more than one DNS A/AAAA Record in your naked domain, pointing to different IPs please remove all of them, except the one for NakedSSL. If after doing this the issue is not resolved within a couple of hours, then please write us an email to hello@nakedssl.com indicating the domain you’re having troubles with.
Usually this process takes between 10 mins and a few hours. However, in some cases it might take a bit longer, for instance if your domain registrar / name server provider does not offer instant DNS changes.
In any case, we recommend waiting for up to 24h before panicking, as DNS changes can sometimes be a bit slower. If after doing the changes and waiting 24H you still don’t see any progress, check that the DNS changes are indeed applied and live – you can do that using this service. If they are applied and live but you still experience issues, please get in touch.
For security reasons we do not allow users to be redirected from a secured connection to non-secured one. We'd strongly advise you to not do this.
NakedSSL will normally take care of automatically renewing all the SSL certificates for the domains added to the system. However, we depend on LetsEncrypt for this, and sometimes we might hit the API limits, so even though it’s rare, it could happen that your certificate is not renewed in time before it expires. If this happens, don’t worry: normally the system will pick it up within 24h and renew it. If that’s still not the case, please contact us at hello@nakedssl.com indicating the domain for which we should renew the certificate.