I have mentioned moving all my websites to the HTTPS secure standard over the past few months. Now that Apple has released Mojave 10.14.4 and iOS 12.2, the Secure Website idea has taken on new meaning. What do I mean by that? Let me show you what the newer Mojave and iOS versions do to insecure websites.
Because of the European Union GDPR and for just general security many people are adding code that makes their websites secure. Generally, I think this is a good idea, but in some ways I don’t worry about it too much. Here is my policy when it comes to Secure (HTTPS) websites. If I am using a Banking website or any website where I am going to use a credit card for shopping, I expect it to be Secure (HTTPS). If it is not, then those guys are history!
Here are some examples of this security issue. This website is Not Secure:
You can tell because Safari labels it “Not Secure” in the address bar in macOS Mojave 10.14.4. Here is another example of an insecure website:
Yes, it is an old site that has probably not been updated in a while. Here is a site from my iPad Pro in iOS 12:
Here is the bottomline with these insecure websites. Does it bother me that these sites are “Not Secure”? No, it does not bother me. I am not going to be giving them any of my information and I am not going to be using a credit card there.
Now, here is a typical example of a website that has security features implemented (HTTPS):
There is the familiar padlock symbol indicating a Secure Site.
I am only pointing all this out because the newest, and I presume all future versions, of macOS accentuates the security status of websites you visit in the Safari web browser. There is no need to panic here. You just have to decide what you are comfortable with in your web browsing experience.