Why was port 80 chosen as the default HTTP port and 443 as the default HTTPS port?

Is there a reason or was it is just defined that way?


2 Answers 2


The Internet Assigned Numbers Authority (IANA) is a department of ICANN, a nonprofit private American corporation that oversees global IP address allocation, Domain Name System (DNS), well-known ports and other Internet Protocol-related symbols and numbers.

On March 1990 they published the document RFC1060 where they listed the well-known ports at that time. In that list there wasn't a protocol assigned to port 80. It went from 79 to 81:

79       FINGER     Finger                                
81       HOSTS2-NS  HOSTS2 Name Server                     

So, at that time port 80 was officially free.

In 1991 Tim Berners-Lee issued the first version of HTTP in a document about HTTP 0.9 where he stated:

If the port number is not specified, 80 is always assumed for HTTP.

Then in July 1992 was published RFC 1340 that obsoletes RFC 1060 where appears:

   finger           79/tcp    Finger                            
   finger           79/udp    Finger                            
   www              80/tcp    World Wide Web HTTP               
   www              80/udp    World Wide Web HTTP               

That document makes official the port 80 as www or http. However there is nothing about 443 on that document.

On October 1994 appears RFC 1700 where for the first time appears this:

https           443/tcp    https  MCom
https           443/udp    https  MCom
#                          Kipp E.B. Hickman <[email protected]>

It seems was solicited by Kipp E.B. Hickman who at the time worked at Mosaic, the first GUI browser company that later becomes Netscape.

It's not clear why 443 was chosen, however the previous RFC had a gap from 374 to 512 and in this RFC the space from 375 to 451 was filled. It's very likely that the numbers were simply given in order of request.

  • 5
    There is likely no reason other than "443 was not already assigned", I pick service ports all the time for no specific reason for the number.
    – Johnny
    Nov 6, 2015 at 16:01
  • 3
    Some protocols (FTP being both the most obvious and only example I can think of right now) use two ports. Maybe, they wanted to leave gaps for possible future extensions of existing protocols? Nov 6, 2015 at 17:03
  • 14
    "17 QUOTE Quote of the Day" That is an important port!
    – Almo
    Nov 6, 2015 at 19:27
  • 2
    @A.L there is a gap, you were probably looking at the list of protocol numbers, not the list of port numbers Nov 6, 2015 at 20:09
  • 6
    One thing to consider, is that when these ports were being assigned, transport layer Protocol Development was fast and furious, with academics all over the states working on this or that project. The RFC Editor (Jon Postel) was very exacting in his standards for accepted final versions of specification, so they had knowledge of on-going projects that were in the works, but that might or might not ever achieve formal RFC status, and could then be included in IANA port list. Additionally, it was possible to request specific port numbers if they were unreserved, so they are not in number order. Nov 6, 2015 at 22:16

The answer by jcbermu mentions that RFC 1340 (assigned numbers) had a run of unused ports from 374 to 512, and 443 is right in the middle.

assert https_port == (374 + 512) / 2 == 443

  • what is 374 and 512? Why were they chosen as the lower and upper limit. 512 is still a valid power of 2 and could be an upper limit of a 9 digit number. Sep 11, 2022 at 8:15

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .