Maybe some MITM on your network? Dodgy SSL certs in your OS?
Blogspot is a google operated domain after all.
I don't use Chrome but I find it hard to believe that Chrome now distrusts Google's own CAs. A user errors seems more likely :)
Whatever one thinks of Google, it's hard to not agree that they take security very seriously, both internal and external (and project zero is one of the best thing ever).
Personally, I prefer it that way. Better to see "ahah, Google tells me Google is insecure" than allowing something flagged as bad just because it come from the same mothership.
I completely agree. Don’t think I stated otherwise?
Anyway, I find it hard to believe for any browser to untrust Google’s intermediate CA. And more so for Global Sign.
That said I recon that especially if Chrome started distruating Google CA that we all heard about it ;)
I'm getting a different cert at least. No cert errors.
Both certs have same common name, etc. But that's where the similarities end.
This is the cert I'm getting:
Serial number: 4254239493315191306
Validity: Tuesday, 20 February 2018 - Tuesday, 15 May 2018
Public key: CC 4E F8 20 68 0A 0D BC B4 78 81 CA BF 4A B3 DD 5A CF 51 FC 0C 1A 12 0C C4 DF FD 77 A2 1A 26 30 6A BC 6A 1A DB 3D D6 68 5B 99 20 D0 79 C8 7F FA 5A AC 5D 23 DB B3 13 03 D1 21 A4 9E A6 CC 9E 77 AF 95 FD AA A2 10 E1 94 D4 96 B3 AB 0F F0 0F 34 35 AB 8D 9E E5 40 61 18 8D A0 E0 0D A5 EA D2 E9 8D 7C 45 9F B8 4C 3F 0F DD 84 BB 6A BC 3C FB CF 48 3B D1 66 8C FE 87 79 AA 36 E9 E3 CD 37 05 74 C2 0A B0 1D AC A6 E5 2B 5A 7B C5 BB 57 C5 2C 7A 5E 0B EB DD 9E 80 8D 1F 47 50 38 BB 9A 18 31 78 EE E6 D9 BC D6 D0 EA A6 07 2F 49 6F 47 01 E9 2A 87 DE BE A6 5D 3D CC 3A CA 05 93 C4 C9 00 AB F1 21 16 40 00 25 E5 9C 52 96 EB A7 43 50 05 AC D5 86 C4 A3 01 BA 08 FB EA 72 97 4D C6 49 6E 75 6C 69 BE 7C C1 BB 87 0D 0B 27 54 10 D0 9E 5E FF 12 A0 B8 48 A8 2D B6 1A E0 B7 92 B0 DE AF 3D 5B F9
Signature: 33 53 C2 AD 95 CA 23 A0 0C 36 43 CA 9C 27 B2 2A F1 07 3B 5B A2 11 C3 F0 9A F8 05 31 AB 30 9C 5E BD 8C B3 10 D2 86 BC 17 60 6E 40 55 D4 4B 66 89 D6 D9 8A F6 10 BB 99 B2 E4 54 7A 36 F8 72 2C DA CC 55 B1 16 32 BD C8 DC D0 D8 FE 9E D3 D5 B7 9C D4 F5 00 CD 9E 1A AF 68 4E B8 D7 C5 AD DD C5 8E D9 E2 59 4C 9A A8 DB ED 37 50 11 A8 D9 8D 33 4C 8E 15 5E 27 5E 90 2A E4 6C 5F A0 4D 93 1D 4D B5 5C 9A 2F 83 09 45 59 ED 64 32 0F 80 CA 22 55 DD C1 69 67 A6 EE 10 B6 13 70 C6 CE 9B 92 D7 DD 29 EE 1B 02 9B 29 90 E5 51 2D D1 5B D2 30 7A 67 49 9F 11 CB 4B 9F E7 3B 2C 1A 34 AD EC B4 1D FE B5 2A D7 12 B2 A7 2D 2B C3 84 0B 13 46 19 A7 3E CA AB D2 FB C8 25 52 E7 56 18 A8 A4 6E 3B 54 BB 82 63 8D 70 9F 49 6B ED 85 70 43 56 ED D6 D3 DA F3 A9 DD 76 26 08 26 AF 35 8F 03 E1 35 5E AD 7F 2C
Perhaps Google uses multiple certs with same Common Name on different servers. If so, I wonder if there's some security benefit.
Or what could the reason for that be?
> You cannot visit calculatedimages.blogspot.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.