Online Tool Store
· 2 min read
How to Reference Common Network Ports
Heshan Fernando
Co-founder & COO
You need a port number and do not want to hunt through docs every time. Some services show up constantly, and it is easier when the common ones are in one place.
A common port reference keeps the obvious ones close at hand.
What port referencing actually involves
The tool is basically a quick lookup of well-known ports, their protocols, and the usual service names associated with them.
That is useful when you are configuring, troubleshooting, or explaining a network checklist.
Why people get stuck here
- Port numbers are easy to mix up.
- TCP and UDP are not interchangeable.
- Service names help, but only when the mapping is clear.
- A quick reference is faster than searching each time.
What a good reference looks like
The port is easy to find
You want the number quickly, not after a long search.
The protocol is visible
TCP and UDP should be part of the lookup.
The service name is familiar
That makes the reference easier to remember.
| Port | Protocol | Common Use |
|---|---|---|
| 22 | TCP | SSH |
| 53 | TCP/UDP | DNS |
| 80 | TCP | HTTP |
| 443 | TCP | HTTPS |
Common mistakes to avoid
- Assuming every service uses TCP only.
- Memorizing the port without the protocol.
- Looking up a number and forgetting the service name.
- Using the wrong port in a firewall or checklist.
- Treating a quick reference as a full network audit.
How to do it with Common Port Reference
Online Tool Store’s Common Port Reference keeps frequently used ports in the browser.
- Open the reference.
- Search for the port or service you need.
- Check the protocol and typical use.
- Copy the number into your notes or config.
That is the fastest way to avoid guessing at common values.
Final thought
If you use the same ports often, keep the reference handy. A quick lookup beats a memory test every time.