443 is more likely than a random port to be allowed through a firewall, for example.
The main reason I would think it's a good choice is because if you decide to get a CA certificate later, you just drop it in and you're done; no additional configuration required.
If you don't have a CA certificate, you're probably not advertising your https:// URLs anyway, so unless search engines are aggressively looking/prioritizing for https transport, it wouldn't seem to hurt anything to run a self-signed certificate there.
Re:Opportunistic Encryption for Firefox
by Dylan16807 on Friday March 27, 2015 @04:17PM
(#9278732)
HTTPS everywhere. And I would not trust an entire site to go unindexed.
There's a lot more to change if I want real HTTPS support. Changing a single port number is the least of my worries.
If it's self signed, and going to throw massive warnings with a direct connection, shouldn't you use anything other than 443?
Any subtleties I should be aware of?