That's not how 2FA works
This is a good article about the weaknesses of the trust models of navigation on the web. The author uses a password manager that also fulfills the role of a personal &#x27;have I seen this site before?&#x27; database, which helps them associate a URL to its conceptual entity, in their quest to determine if the site they visited was the site they intended to visit.<p>In this exact form, this is a feature that&#x27;s absent from mainstream browsers today. Because browsers do not have this, people instead turn to all sorts of other signals to judge the site&#x27;s identity, but each one of those signals is designed for another purpose, and ought to not to be used directly by the user to make such determination. But no other signals are available, so they get used nonetheless.<p>Some people look at the URL before clicking it, or the URL bar in the browser after they&#x27;ve already navigated to the site, and try to judge from the URL whether the site belongs to the entity they intended to visit. This is fallible for a bunch of reasons, including: (1) people often read visually instead of comparing codepoint-by-codepoint, so reading errors or homoglyph attacks are possible, and browsers can only meaningfully mitigate against the latter; (2) very few people keep a computerized allow-list, so they check against expectations in their head; and (3) some organizations will make use of domain names that greatly differ from their own name, which works contrary to the instinct of a URL-judging user who consider themselves &#x27;cautious&#x27;, and it&#x27;s difficult to stay aware of all this.<p>Some people look at the TLS certificate, and try to judge from the information displayed by the browser about the cert whether the site belongs to the entity they intended to visit. This is fallible for a bunch of reasons, including (1) DV certs only prove that someone (i.e. anyone) had control of the domain at the time near the cert&#x27;s issuance, so its value as a trust signal to the user ought to be zero and immediately reduce to the prior case of mentally validating the URL by its character content; (2) EV certs validate against a legal entity in some jurisdiction, but as the &#x27;stripe.ian.sh&#x27; stunt has demonstrated, jurisdiction-by-juristiction registries of legal entities are a tool for a different use-case and were never intended to collectively ensure globally unique Organization names; and (3) in their rush to ensure widespread TLS deployment on all sites, and their involvement with efforts to bring short-lived cost-free DV certs to everyone, browser-makers began de-emphasizing the UI distinctions between DV certs and EV certs some time before the true shortcomings of EV as a user-facing trust signal were widely demonstrated.<p>Some people look for the visual design of the website. This is trivial to fake.<p>Some people will rely on browser-resident bookmarks, browser history, or &#x27;top sites&#x27; tiles to navigate to common sites they&#x27;ve visited before (or to sites the browser-maker pre-loaded into the listing). This is a great way to preserve the trust chain and reduce the likelihood that the user arrives at an unintended site by mistake. But these features do not directly address the case of a person navigating to a URL they were linked or provided from an arbitrary source, such as the example raised in the article.<p>Building blocks exist today that could be used by publishers and browser-makers to aid users in judging URLs. Some of these will require past UX decisions to be undone.<p>For example, top sites could become their own Root Certificate Authorities [1] and be listed in browser trust stores; these companies would be expected to issue certs for sites associated to themselves. This would eventually reshape the cert landscape so that a parent-child relationship between issuer and subject could be meaningfully distinguished from a &#x27;provider and customer&#x27; relationship. Companies that provide services to others, such as payment processors, could also become root CAs and sign for their customers. These changes, and a browser UX that once again shows the cert issuer, would go a long way towards reducing the likelihood that users are fooled by sites trying to impersonate top sites.<p>If this were to come to pass, other CAs would be expected to pivot to minting certs that play the role of a trustmark, by conferring a degree of ongoing assurance that&#x27;s useful to the user (which, in fairness, was the original point behind EV certs). They would do this by establishing strong brands around their trustmark, issue certs for a short lifetime, and monitor the site on an ongoing basis to see if it&#x27;s still deserving of their trustmark. This would result in a business model similar to those of EV certs, but a trust model that&#x27;s based on the user&#x27;s trust in the CA&#x27;s exercise of good judgment befitting their brand.<p>[1] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=13495262" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=13495262</a>