Most of the existing PaaS out there let you use your custom domain with SSL, but lots of DNS and domain providers still do not allow CNAME or ALIAS records on the naked domain, which makes it hard –or impossible– to install an SSL certificate and redirect all the traffic on your naked domain without having a custom IP. NakedSSL came to fix that.
@daniel_roger_casanova Hi Daniel! You can use it for sure :) You just need to ensure that your naked domain (yourdomain.com) is pointing to the IP that NakedSSL gives you, while the "www" version (www.yourdomain.com) is pointing to the web builder.
@alexandergerund@jacqvon Hi Jacqueline! We built it to solve a simple problem: while it's a good practice to redirect your naked domain to the "www" version of it (more info here: https://www.yes-www.org/why-use-...), it's not easy to do it under SSL when using PaaS like Google App Engine, Heroku or Now.sh, as lots of DNS management services are still a bit limited on that. We stumbled upon this issue a few times already and although is pretty easy to solve, it's tedious and requires some time, so we decided to create a service to automate it for ourselves – and that finally turned into this product.
@kehers Hi Opeyemi! Really good point, thank you! Although this is a very first version that we built in barely 4 weeks focusing just in the basics, that's one thing we still need to add for sure :).
Solodoers
NakedSSL
Product Hunt
NakedSSL
Mailintel
NakedSSL