NakedSSL

Hassle-free SSL clothes for your naked domains.

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.

discussion
Would you recommend this product?
4 Reviews5.0/5
Daniel Roger Casanova
Love for business, design and technology
Hello, can I use this if I'm using a web builder or will having two a records pointing to different IPs conflict?
Upvote (3)
Share
Jesús Espejo
Maker
Partner Tech & Strategy @ okay bueno
@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.
Upvote (2)
Share
Opeyemi Obembe
/everygood.co
Including a short "how it works" on the homepage wont be a bad idea.
Upvote (3)
Share
Jesús Espejo
Maker
Partner Tech & Strategy @ okay bueno
@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 :).
Upvote (1)
Share
Primer
Founder of Division 77
I think this may have come a bit late for me as I resolved the issue with a crappy .htaccess hack, but I run my stuff on Heroku and it was very difficult to get all traffic to redirect to the SSL version of my site. I'll check this out for sure.
Upvote (2)
Share
Jesús Espejo
Maker
Partner Tech & Strategy @ okay bueno
@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!
Upvote (1)
Share
Primer
Founder of Division 77
@jespejo Trying to register. Don't seem to be getting my account verification email.
Upvote
Share
Jesús Espejo
Maker
Partner Tech & Strategy @ okay bueno
@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.
Upvote
Share
Primer
Founder of Division 77
@nakedssl @jespejo getting an error trying to add domain: "The redirection field format is invalid"
Upvote
Share
Primer
Founder of Division 77
@nakedssl @jespejo I think it may be because I have a .rocks TLD
Upvote (1)
Share
Jacqueline von Tesmar
Community at Product Hunt ⚡️
Hey @alexandergerund & @jespejo, Can you tell us more about why you wanted to build this?
Upvote (1)
Share
Jesús Espejo
Maker
Partner Tech & Strategy @ okay bueno
@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.
Upvote (3)
Share
This looks pretty cool. What differentiates you guys from Cloudflare?
Upvote (1)
Share
Jesús Espejo
Maker
Partner Tech & Strategy @ okay bueno
@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.
Upvote (2)
Share