NakedSSL

@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 :).

@mickc79 Hi Mick! That is exactly the issue we've been running over and over again, so we decided to give it a try to solve it :) If you decide to use it we would love to hear your feedback!

@jespejo Trying to register. Don't seem to be getting my account verification email.

@mickc79 We leverage AWS SES for transactional emails, so sometimes they might take a couple of minutes to send them :) Or maybe it went to SPAM, could you please check it? In any case, if you haven't got anything in the next 5-10 mins just write us to hello@nakedssl.com and we can confirm your account from our dashboard.

@nakedssl @jespejo getting an error trying to add domain: "The redirection field format is invalid"

@nakedssl @jespejo I think it may be because I have a .rocks TLD

@etc Hi E.T.Cook! Thank you :) It's actually pretty different: CloudFlare offers full DNS management (among other services), so they actually resolve your domain names. CloudFlare lets you add ALIAS/CNAME records pointing to hostnames directly on the naked domain –also with SSL–. If you use CloudFlare (or any other modern DNS service), then NakedSSL is useless as you can solve the problem at DNS level. Unfortunately, not always you can choose the DNS manager service for your domains –especially if you work with customers–, and lots of the DNS management services still do not let you add ALIAS/CNAME pointing to hostnames on naked domains, and if they do, they don't support SSL through it. This is a problem if you use PaaS like Heroku or Now.sh, as you would be able to resolve https://www.mydomain.com, but trying to access https://mydomain.com would give you an error. NakedSSL solves exactly that problem in a pretty simple: it gives you a static IP that you can point your naked domain to, and the system takes care of setting up an SSL certificate (through LetsEncrypt) and the redirection for it.

@ckramer Hi Kramer! Good point :) That resolves just the naked domain, but not the naked domain under SSL – http://yourdomain.com will work, but not https://yourdomain.com. NakedSSL addresses exactly that.

@jespejo you are absolutely correct. I didn't even notice that this was still an issue. When explicitly attempting to navigate to the top level domain with https enforced, the redirect does not trigger. So even though this works for redirecting http://yourdomain.com to https://www.yourdomain.com (as long as you enforce SSL on a service such as heroku), it's not a complete solution. I hope you guys can find a way to provide your solution as a heroku add-on to prevent having to depend on 3 parties take care of hosting a simple website (cloud hosting, DNS registration and domain management and your service for top level domain redirect). I have been utterly frustrated with my DNS/domain management party for not being able to provided naked redirect, as it severely handicaps you when you use a service like heroku to host your website accessible through its naked domain.

@ckramer Thank you for your suggestion! We'll definitively study the possibility of adding it to Heroku as add-on. Stay tuned :).

@danielg27890040 Nope, all up and running! If you have issues you can reach out to us at hello@nakedssl.com :)