4 ms·
re 2: you're loading mixed https and http content. open up the devtools console and it will show you what's being loaded over http.
by durkie 12y ago
re 2: you're loading mixed https and http content. open up the devtools console and it will show you what's being loaded over http.
- mappu 12y agoEither that, or they have a SHA-1 certificate that expires in 2016 or later - https://www.ssllabs.com/ssltest/ https://www.ssllabs.com/ssltest/ will tell you for sure.
- dspillett 12y agoThe cut-off isn't 2016-01-01. I have a cert using a SHA1 fingerprint which expires in June 2016 (see https://random.spillett.net/ https://random.spillett.net/) and Chrome is not currently complaining about that.