What Port Lookup helps you do
Search a focused reference of common TCP and UDP ports by port number, protocol, service name or purpose. It is a quick way to identify what a port is typically used for without memorizing the list. The reference covers well-known services rather than the full IANA registry.
The reference is bundled in the page and searched in your browser. No queries are sent to Haivix.
How it works
Most tools here are offline calculators: the address math, RAID capacity, permission bits, TCP window sizing and transfer-time estimate all run in your browser with no request. The RDAP lookup is the exception, because registration data lives in public registries and the domain must be sent to a lookup service. Unit conventions matter throughout: a megabyte may mean 1,000,000 or 1,048,576 bytes, and a megabit is always one eighth of a megabyte. These are reference models, not live checks, so a port can be listed without a service running, a permission mode can be valid without being appropriate, and a RAID estimate can differ from formatted capacity.
How to use Port Lookup
- Type a port number, a protocol or a service name.
- Read the matching entries and their typical purpose.
- Check the protocol column; many services use both TCP and UDP.
- Copy the details into your notes or a firewall rule.
When to use it
- Identify an unfamiliar port seen in a firewall log.
- Check the default port for a service.
- Look up which protocol a port normally uses.
- Confirm a port before writing an allow rule.
- Explain a service to someone reading a packet capture.
- Compare the usual ports for a database and a web server.
When not to use it
- Do not treat the result as proof a service is running.
- Do not use it as a port scanner.
- Do not expect the complete IANA registry or every vendor-specific port.
Example
Searching for 443 returns HTTPS over TCP, while 53 returns DNS over both TCP and UDP. A search for database returns MySQL, PostgreSQL, SQL Server, Oracle, Redis and MongoDB. A registered port can still be reassigned by configuration, so the service name is a convention.
What you can do with Port Lookup
- Search by port number.
- Search by protocol or service name.
- Match words in the description.
- Show the protocol for each entry.
- Return multiple matches for broad terms.
- Work offline in the browser.
Example: check the model against the live system
Note the unit convention before comparing figures. Mbps and MB/s differ by a factor of eight, and MB and MiB differ by about 5 percent.
Treat a lookup as a starting point. A port reference, a permission mode and a RAID calculation all describe expectations, not the state of a running host.
Confirm on the system itself where it matters: ss or netstat for listeners, ls -l for permissions, the controller utility for array status.
Keep RAID in perspective. It protects against a disk failure, not against deletion, corruption, ransomware or a lost site.
Record the inputs alongside the result so a later comparison uses the same assumptions.
Check the time unit on latency. A round-trip time is usually milliseconds, and entering seconds changes the bandwidth-delay product by a factor of a thousand.
Treat registry data as a snapshot. RDAP records can be redacted, cached or updated after a transfer, so confirm ownership and expiry with the registrar.
What to know before you start
- The reference covers common ports and is not the complete IANA registry.
- A port can carry any service if both ends agree, so the name is a convention, not a guarantee.
- It does not scan, probe or test connectivity.
- Ephemeral and vendor-specific ports are mostly absent.
Common mistakes
- Assuming the listed protocol is the only one a service can use.
- Treating a common port as a security guarantee.
- Expecting an uncommon vendor port to appear in the list.
- Forgetting that both ends can agree on a non-standard port.
Troubleshooting
If there are no matches, try a shorter term or the port number.
If several entries appear, read the protocol and description columns.
If a service is missing, it may be outside the common reference.
If the port is open, that is a live finding and not something this reference can confirm.
Related standards and documentation
- RFC 791 defines IPv4 addressing and packet format.
- RFC 9293 defines TCP, including the receive window and its scale option.
- IANA maintains the Service Name and Transport Protocol Port Number Registry.
- POSIX and the Single UNIX Specification define the permission bits behind chmod.
- RFC 9082 and RFC 9083 define the RDAP query and response formats.
- IEEE 802.3 defines the Ethernet frame sizes behind the common 1500-byte MTU.
- Check bits versus bytes.
- Verify on the host.
- RAID is not backup.
- Keep the inputs.