Outlook sign in page is not secure when using Google Chrome

I had the same issue  today...the first time ever with Outlook.

I had been using a shortcut on my desktop for a VERY LONG time without issue.

The shortcut directed me to:  https://bay175.mail.live.com (with a very long list of numbers and characters) - which has always worked

I used the Google Search for:  Outlook.com

That search provided this site:  https://outlook.live.com/owa/

I now have a new shortcut on  my desktop:  https://outlook.live.com/owa/ - and there are NO issues

Abigail...my Google Chrome browser is indeed up to date. What I meant by the "insecure" sign-in page for Outlool.com is that before the HTTPS...there is a padlock with an orange triangle over it. I'm with the understanding that there is no SSL or whatever on that page. I don't want to run the risk of signing into my Outlook.com email if that page puts me at risk for my password to be exposed out onto the internet.

As mentioned in my last note, I'm somewhat computer saavy, but not when it comes to this sort of thing. I wouldn't even know where to begin to do anything with 'certificates'...etc.

Thanks for getting back to me so quickly. I look forward to whatever you might suggest.

Cheers!!

I just started  having this problems as well. With my email, some financial accounts, etc.,. I did find this article about changes by Chrome in 2017.   Additionally  I read something about my LAN and Wifi Router needing to be reset.  I am not a WHIZ KID and don't quite follow how to insure SSL

_________________________  What does it all mean.  What am I to do? Should I reload Chrome?

https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn

As announced in September, Chrome will soon mark non-secure pages containing password and credit card input fields as Not Secure in the URL bar.

This document is intended to aid Web Developers in updating their sites to avoid this warning.

Enable warnings

Warnings will be enabled by default for everyone in Chrome 56, slated for release in January 2017.

To test the upcoming user experience before that time, install the latest Google Chrome Canary build.

To configure Chrome to show the warning as it will appear in January 2017, open chrome://flags/#mark-non-secure-as and set the Mark non-secure origins as non-secure option to Display a verbose state when password or credit card fields are detected on an HTTP page. Then relaunch your browser.

You can see an example of the browser’s warning behavior on this page.

When the Not Secure state is shown, the DevTools console shows the message This page includes a password or credit card input in a non-secure context. A warning has been added to the URL bar.

The problem is that outlook.com is signed by a chain of certificates where the 2nd one is an older Baltimore CyberTrust Root  version 3 signed by GTE CyberTrust Global Root, but signed using SHA-1

PKCS #1 SHA-1 With RSA Encryption

This is results in this warning

SHA-1 Certificate

The certificate for this site expires in 2017 or later, and the certificate chain contains a certificate signed using SHA-1.

Hi,

I am glad to assist you with your issue. I understand that you are having problems having secured browsing on Outlook sign in page usng your Google Chrome browser. I suggest that you reset and update your browser and see if the issue will still persist.

Also, you mentioned that you've noticed that the sign-in page for Outlook.com (when trying to sign into email) is not secure. Please provide us detailed description on what happens when you say you are having unecured browsing with Outlook.com.

Please post your response here.

Thanks!