Thank you for the follow-up. I took a look and I see the links that you're talking about.
These links are custom URLS that we inputted into our SmarterTrack instance.
I will talk with my team about getting these URLS changed to HTTPS.
As far as SmarterTrack itself goes we are not loading HTTP resources into the HTTPS page thus breaking the HTTPS. So overall this isn't a bug but just a configuration issue on our side.