<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br><blockquote type="cite"><div><div><blockquote type="cite">Lemme see; we've spent 3 decades trying to set up a cryptographically secure DNS<br>to make sure that www.bankofamerica.com (http://www.bankofamerica.com) resolves to an actual instance of a BOA<br>server, ...<br></blockquote><br>No, it just ensures that the server is under the same control as the bankofamerica.com domain<br>name. As I said in another part of the message you quoted, you can't tell by looking at a<br>domain name who owns it. You can guess, sometimes you guess right, sometimes you don't.<br></div></div></blockquote></div>Beyond which, as I'm sure you know, email "domains" are defined by MX records, not even the address records that web addresses are based on. <a href="https://www.bankofamerica.com">https://www.bankofamerica.com</a> and email:<a href="mailto:some@bankofamerica.com">some@bankofamerica.com</a> may - and probably do - end up at entirely different places. (In fact, they do: The MX record for <a href="http://bankofamerica.com">bankofamerica.com</a> goes to <a href="http://pphosted.com">pphosted.com</a> - i.e., ProofPoint, which serves as the mail front end for most large businesses these days.)<div><br></div><div><div> -- Jerry</div></div><div><br></div></body></html>