What? Writing raw onion addresses is like writing raw IPv6 addresses. Nobody can remember then and check them.
What is easier
or
> ej3kv4ebuugcmuwxctx5ic7zxh73rnxt42soi3tdneu2c2em55thufqd.onion
0: https://community.torproject.org/onion-services/advanced/oni...
Exactly the same guarantees are also achieved by putting your clearnet address on HSTS Preload lists, or by writing https:// in front of the url on the users side.
With https you need to get the address over a secure channel and hope that no CAs are compromised. The secure channel might be easier (because you can quickly memozrize twitter.com) but to avoid the second you need some complicated and not officially supported certificate pinning.
Perhaps next you’ll wonder if it’s as simple as compromising a CA and a CT log? Nope, as browsers require cryptographic attestations from multiple CT logs. If you’re using Chrome, one of those logs has to be the one operated by Google.
Also such collusion will soon be defeated by SCT auditing https://www.hardenize.com/blog/certificate-transparency-sct-...
https://docs.google.com/document/d/16G-Q7iN3kB46GSW5b-sfH5MO...
And you cannot really check if it's the correct one.
At least on regular net, you have a chance to spot nytime5 is fake.
It is not possible to squat onion domains for typo errors like you can clearnet addresses.
Similar to bitcoin, one character swapped breaks the hash-checksum, making the address 99.99999999% likely to be invalid.