Certificates address the area of "non-repudiation". The reason for this checking is to prevent potential Man in the Middle attacks, where an attack could have a perfectly valid certificate, but it isn't issued to the website you are attempting to visit. Most major accepted TLS/SSL certificates are issued to host names, which can be looked up via DNS. If you need to access a site that is not in DNS, and you must use https, and you don't want to see that error, I suggest you use a host entry.
Generally speaking, a CA will not issue a cert for an IP address. This indicates that the site you have reached cannot prove that it owns 66.33.204.254.
Since you entered 66.33.204.254 but the certificate was issued to you will get the error. Whenever they do not match, it will display the error that you are seeing. To protect against this, your browser will automatically check the address that you entered against the certificate. Your communications are still encrypted, but they are being sent to (and decrypted by) an unknown entity. Instead, your communications have been intercepted in what is known as a Man in the Middle(MitM) Attack. You check the certificate for the connection and discover that it was actually issued to This is a strong indication that your browser hasn't actually reached. The error indicates that you have reached a site that cannot prove it owns the address that you entered in the address bar.
0 kommentar(er)
