March 24th, 2020 at 10:14 PM
As Lain said, we don't have the SSL certificate yet, and as such it's throwing the warning. It's planned in the next couple of months when we move to our new server.
In the past several years, more and more websites have moved to SSL. In the past, most websites weren't, and browsers didn't throw the warning for non SSL websites. Now, we're a little behind the curve (and hence browsers feel more comfortable putting those out there). We will be addressing it soon!
In the past several years, more and more websites have moved to SSL. In the past, most websites weren't, and browsers didn't throw the warning for non SSL websites. Now, we're a little behind the curve (and hence browsers feel more comfortable putting those out there). We will be addressing it soon!
