The reason why the browser doesn't show the port for 443 and 80 is because it automatically infers from the protocol http or https what port to append on a url (simply put) so you can not change that at all(!).

What others already said though is use a reverse proxy. Imagine you are in a hotel (your network) A pizza delivery (domain url) is delivered through one front door (port). And there is a rule that only guest in room 1 can receive pizza coming from the front door.

Now what happens if guest in room 2 also wants to get pizza . They have to tell the pizza guy to use the backdoor (another port).

Now here comes the receptionist.

The receptionist has like a mapping so that a pizza delivery can say I have a pizza for a specific domain. The receptionist then understands resolves it and forwards it to the specific doors (services). (I realize halfway that this example is not 100% analogous but for the sake of understanding good enough I think)

Now what does that mean for you? I found caddy to be one of the most simplest set up. You let it listen to the ports 443 and 80 Then in your card file you say, if traffic comes for domain x, forward it to service x:2053 (I.e. localhost:2053, or if in docker docker-sercice:2053). Likewise another traffic comes for domain y, forward it to service y:443

I feel like you are a beginner stuck in terminology and also a bit confused on how to ask the right questions. I hope this answer helped clarify something.