[redpepperracing]

If I can take a guess at what you are referring to, in Chrome (and Edge since it is based on Chrome) the default for the last few years is to assume all sites should be encrypted, regardless of the site function. it used to be that you only encrypted pages that were for sensitive information (payment details, personal info, etc), which at the time was a bit more hardware intensive on the server side, which is why it wasn't the default. Now handling encrypted data is much less resource intensive (mostly because the hardware is exponentially faster, but also there are dedicated hardware ASICS for it, if you do heavy encrypted data processing) and is inherently more secure, so any site that isn't encrypted now gets flagged as such, as you are seeing. If you inspect the site URL you will see it starts with http:// which means it is not encrypted. Encrypted sites would start with https:// You can see the difference if you go to the Pelican main site which is encrypted on all pages.

In this case, there isn't a whole lot of risk in using the site unencrypted, the very slight risk being if someone did happen to snoop your data (say over a public WiFi network) they could see your username and password being sent in clear text. If you use different passwords across sites, you should not have too much to worry about, but making that determination is up to you.

I have no issues with it personally. I should also say that the people running this site should be able to switch it over to an encrypted site fairly easily, so I'm not sure why they haven't.