# URL Ports ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/media/uploaded_book_covers/profile_1300767/learn-http-clients-golang_wrRbact) ## Metadata - Author: [[Boot.dev]] - Full Title: URL Ports - Category: #articles - Summary: A port in a URL is where network connections are made, numbered from 0 to 65,535. Most websites use default ports 80 for HTTP and 443 for HTTPS, so you usually don't see them in the URL. If you use a different port, like 8080 for testing, you must include it in the URL. - URL: https://www.boot.dev/lessons/acb29296-b5c9-4449-a5c4-e0735bf3f787 ## Highlights - The port in a URL is a virtual point where network connections are made. Ports are managed by a computer's operating system and are numbered from `0` to `65,535` *(Though port `0` is reserved for the system API)*. ([View Highlight](https://read.readwise.io/read/01jwcdfxxp58w5m8de36z2r26z)) - Whenever you connect to another computer over a network, you're connecting to a specific port on that computer, which is listened to by a program on that computer. A port can only be used by one program at a time, which is why there are so many possible ports. ([View Highlight](https://read.readwise.io/read/01jwcdgzp27ee70b2x7hq5010h)) - The port component of a URL is often not visible when browsing normal sites on the internet, because 99% of the time you're using the default ports for the HTTP and HTTPS schemes: `80` and `443` respectively. ([View Highlight](https://read.readwise.io/read/01jwcdhf1mxb4tvcye48nh8sje))