I would <i>love</i> to switch the whole site to https, but it&#x27;s not that easy.<p>The login request is always sent via https, even when you are using the site over plain http. So your password should always be encrypted.<p>The site does work over https (try it - <a href="https:&#x2F;&#x2F;readlang.com" rel="nofollow">https:&#x2F;&#x2F;readlang.com</a>), and at one point I redirected all http traffic to https, but there was a big problem. I use external dictionaries in an iframe to provide additional definitions and these are almost always only available over http: <a href="https:&#x2F;&#x2F;readlang.uservoice.com&#x2F;knowledgebase&#x2F;articles&#x2F;279539-changing-the-dictionary" rel="nofollow">https:&#x2F;&#x2F;readlang.uservoice.com&#x2F;knowledgebase&#x2F;articles&#x2F;279539...</a><p>It worked OK for a short while, but then Chrome and Firefox both refused to display http content within a https page. Chrome displays a very subtle shield icon that the user must click on to reload the page allowing mixed content. This is far too unfriendly to expect my users to do, so I had to resort to using http again :-(<p>Of course, the ideal solution would be for me to have access to dictionary definitions so I could integrate them properly instead of using an ugly iframe, but with 50+ languages supported, that&#x27;s a tall order!