If you don&#x27;t have a way to confirm that the key you&#x27;re seeing from the other site is right, you&#x27;re inherently vulnerable to a man-in-the-middle attack which removes the benefits of the encryption against the attacker.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Man-in-the-middle_attack" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Man-in-the-middle_attack</a><p>httpS:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Zooko&#x27;s_triangle<p>It&#x27;s not clear that the certificate authority system was or is the best solution to this problem, but it is a problem that calls for <i>some</i> solution. In the case of Domain Validation, we only try to confirm that the key is appropriate to use with the domain name, which is the smallest possible kind of confirmation that can be done to address the crypto problem. There&#x27;s no attempt to validate or verify anything else about the site.