Our FAQs

Since we started we have always offered a redirection for free for one single domain. While most of our users use our service for a legit reason and comply with our T&Cs, some people with bad intentions have heavily abused our free plan and we are obliged to halt the free usage of our service – hopefully only temporarily until we find a solution.

The main reason for this has been usage of our service to redirect sites dedicated to phishing, hacking, and other illegal activities, ranging from using registered trademarks to linking to services that allow the download of copyrighted files. This resulted in a degradation of the quality of the IPs, affecting the trust level of all the domains hosted in the instance with that IP. Obviously, this resulted not only in complaints from our users, but most importantly: in several warnings from AWS (our IP provider) about these infringements. Our support team found itself dedicating most of their time to solve issues arising from these illicit usage of our free service, which is not only not sustainable for a business but also not fair for the rest of our users. Therefore we are obliged to halt the free plan until we find a solution to this issue.

Users that already have a domain added for free are not affected and can still use the service as usual. For those that still want to host only one domain in a legit way, we're now offering a low-cost single domain plan.

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.

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.

Absolutely not. If you do that, NakedSSL won’t be able to redirect your domain and the SSL will never renew again. You must keep the NakedSSL IP in your domain as long as you want to keep using the service.

Unfortunately this isn't technically possible. If you need to make changes in your domain or its settings (STS, caching, redirection, etc), you will have to remove it and re-add it again.

TLDs and domain names are tricky. It’s almost impossible to cover all of them because they can be almost infinite, especially taking into account uncommon characters, non-Western alphabets, etc. Therefore we do not provide a list of supported domain formats/TLDs. We’ve tried to cover most of them but if you discover that you need to add a domain format or TLD that does not pass our validation check, please send us an email to hello@nakedssl.com with the details and we’ll evaluate if and how we can support that format.

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.

Yes. If sharing the servers with multiple users is a concern for you, your company or your clients, we also offer dedicated instances that could run our software, but just for your domains. Same interface, same API, but your domains are isolated from the rest in an instance dedicated exclusively for you but managed by us. For inquiries and more details, reach out to us via hello@nakedssl.com.

Nice to hear that! Spread the word; tell your colleagues how awesome NakedSSL is. If you’re in Berlin, pass by our office and have a coffee with us. And if you’re a maker, check out our parent’s company studio – maybe we can work together.

If you have a paid plan, you’ll see a chat bubble directly from your dashboard, so you can write us directly there. We normally answer within 24H during working days. If you do not have a paid plan, just write to hello@nakedssl.com – but please ensure that you’ve tried to troubleshoot your issue with the details explained in this FAQs. We host thousands of domains for free and unfortunately we can’t offer customised support to each of you, so please ensure that you have used all the tools at your hand before requesting support from us. Do not forget to include "I have read the FAQs" in your request ;).