Port Lookup
Search the common TCP/UDP port reference database by port number or service name. This is a lookup tool, not a scanner — it never probes any live host.
Input
Results
Overview
The Port Lookup is a searchable reference of 65 commonly used TCP and UDP ports. Enter a port number to see which service normally uses it, or type part of a service name to find its usual port.
It is for quick recall during troubleshooting, firewall rule reviews, and documentation. It is not a port scanner: it never contacts any host and cannot tell you whether a port is open anywhere.
How It Works
Ports are 16-bit numbers (0–65535) that let a host direct traffic to a particular service. Ports 0–1023 are the "well-known" ports, 1024–49151 are registered, and the rest are dynamic or private. The Internet Assigned Numbers Authority (IANA) maintains the Service Name and Transport Protocol Port Number Registry.
This tool searches a short list bundled with the page. A number search returns exact matches; a text search matches any service name containing your text (so http finds HTTP, HTTPS, and the alternate HTTP/HTTPS ports). Descriptions are not searched. Everything runs in your browser.
How to Use the Port Lookup
- Type a port number such as
443or a service name such asSQLin the search box. - Press Calculate.
- Read the matching rows: port, protocol (TCP, UDP, or both), service, and a short description.
- Use the result as a starting point and confirm unusual cases against the official registry.
Worked Example
What uses port 53, and which database uses 5432?
You see traffic to port 53 in a firewall log and need to confirm what it is, then check the usual port for PostgreSQL.
Input
Search 1: 53
Search 2: postgres
Output
53 TCP/UDP DNS Domain Name System resolution
5432 TCP PostgreSQL PostgreSQL database default port
Port 53 is DNS, and the protocol column reads TCP/UDP: DNS normally uses UDP for ordinary queries and TCP for large responses and zone transfers, so a firewall must permit both if resolution is to work reliably.
Knowing the conventional port is only a hint. A service can be configured to listen on any port, and traffic on a standard port is not guaranteed to be that protocol.
Interpreting Results
- Protocol
- TCP is connection-oriented; UDP is connectionless. "TCP/UDP" means the service is commonly offered over both.
- Service and description
- The usual application associated with that port by convention.
- Multiple rows
- Some ports are shared by related services, and a service-name search can match several ports.
Troubleshooting
- "No matching ports found in the reference database."
- The list is limited to 65 common ports. Try a shorter service name, or consult the IANA registry for less common ports.
- The service I see on a port is not what the tool says.
- Services can run on non-default ports and malware often uses well-known ones. Identify the actual process or protocol with a packet capture or the host's connection table rather than trusting the number.
- I need to know if a port is open.
- This tool cannot test that. Use a client from a network you are authorized to test from, such as
nc -vz host portorTest-NetConnectionon Windows.
Limitations and Accuracy
- The list contains 65 entries — common services, not the full registry.
- Text search matches service names only.
- Port numbers describe convention, not what is actually running.
- Nothing is scanned or probed.
Data Handling
Runs in your browser. What you enter is processed on your device and is not sent to NetEngToolkit’s servers or to any third party.
Frequently Asked Questions
Is this a port scanner?
No. It is a lookup table and sends no traffic to any host.
Why do some services list both TCP and UDP?
They use different transports for different purposes. DNS, for instance, uses UDP for most queries and TCP for large or reliability-sensitive exchanges.
What are ephemeral ports?
High-numbered ports a client picks temporarily as the source of an outgoing connection. They are not listed here because they are not tied to a service.