Using HTTPS by Default
During the private beta, we asked our users to give us feedback about our application. And one of the feedback was something like :
Your application sounds great, but there’s no chance I’m going to sign up over an unencrypted connection.
And this user was absolutely right. We had planned to configure HTTPS... someday. But your security is important right now!
So, the right thing has been done, and now Translation.io uses HTTPS by default.
This applies to both web pages and API calls.
The good news, for us, is that Google uses HTTPS as a ranking signal with a small indexation boost. So it's a typical win-win situation!