Yes this is due to some the server allowing old https connections. I'm hoping to have a test site up for some testing this Thursday to be tested before we migrate to a new platform, server etc. That should deal with this issue and many others.
Thanks, Fred. I wasn't sure if it was correct or a "false negative" from Brave. I only started using Brave last month so I'm having to learn its notification system. This isn't the only site on which I'm seeing this.
Fred, Brave is still saying the site is "Not Secure" up in the Address Bar. Wasn't this new platform supposed to fix that?
Update: The above was using a regular browser window.
I then opened a "New Private Window with Tor" and logged into the site from it where I am now doing this update. In this Tor-enabled private window, I'm still seeing the "Not Secure" in the Address Bar.
The site is secure, the issue is the image showing it is insecure is pointing to a site that doesn't use https and thus the browser is warning you that something is insecure on the page. If you go to the main page you won't see that. That indicator just confirms that if ALL of the traffic to that page is transmitted via a secure method. Previously we used an older protocol as well and that caused issues.
If you were using doing something like banking I would be concerned about that, but on pages with images it is OK.