Huh. HTTP works, but HTTPS does not.

HTTPS for dotless domains (a bit of a misnomer but it can help in finding good reading material about it) should also work fine on the same browsers. That said, most dotless domains don't run it because they've historically not been given certs due to security concerns. As an example: https://uz./ likely just had the *.cctld.uz cert applied to the whole virtual server block and uz was just one of the names assigned to that block.

Bonus fact: https://. works on Firefox (triggers an A/AAAA DNS query for root) but not Chrome.

This may be an antifeature if someone's environment has a host on the LAN named amazon.

Note the trailing ., it's an FQDN. Your system/application shouldn't use search domains if provided a fqdn.

hence under a properly set up DNS and application: system with search domain for `.internal` and a host named `amazon` will be hit the internal host for `https://amazon` and `https://amazon.internal` but not `https://amazon.`