Chrome show https invalid, but says that the certification is valid
-
4A side note: A payment provider with a let's encrypt certificate? That smells like phishing.– Gerald SchneiderFeb 11, 2019 at 7:05
-
2Check the developer console (F12). Most probably some resource (image,js, css) is loaded via http.– Gerald SchneiderFeb 11, 2019 at 7:15
-
What do you see when you click on the "Not Secure" warning to the left of the URL?– NickFeb 12, 2019 at 11:32
Add a comment
|
2 Answers
The URL you are visiting is www.paykey.com
. The certificate is issued to paykey.com
. The certificate does not contain www.paykey.com
in the Subject Alternative Name field.
Therefore, there is no match. Strict browsers will raise an error in this case.
-
Letsencrypt is an awesome, free & opensource ssl provider. But you have to pay for wildcard ssl (*.domain.com). Here, the certificate issued for www.paykey.com & you are browsing paykey.com with that certificate. Either need to get free letsencrypt cert for www.paykey.com + paykey.com or purchase *.paykey.com OR use www.paykey.com and redirect all requests from paykey.com to www.paykey.com– AntoFeb 11, 2019 at 18:10
-
This is a wrong answer, this happens with both domains - see updated question Feb 12, 2019 at 11:22
-
@EliaWeiss The certificate SAN field does not contain www.paykey.com, so strict browsers will still raise an error when visiting that domain. See the "Common Name Support Removed" section here: thesslstore.com/blog/security-changes-in-chrome-58 Feb 12, 2019 at 15:35