Port Lookup
Look up TCP, UDP, SCTP and DCCP port assignments from the IANA registry. Search by port number (443), service name (https) or keyword, and filter by protocol and port range.
Input
Search by port number (80), service name (http) or a word from the description (web server). Case-insensitive.
Output
| Port | Protocol | Service Name | Description | Range |
|---|---|---|---|---|
| No data yet | ||||
Guides
Port Lookup is a searchable reference for network port assignments. Type a port number, a service name, or a keyword and instantly see which service uses that port, over which transport protocol, and where it sits in the IANA port ranges. The data covers every assignment in the IANA Service Name and Transport Protocol Port Number Registry — 12,557 entries across TCP, UDP, SCTP, and DCCP.
How to use it
- Search by one of three things:
- a port number —
443,22,3306— returns the exact port's rows for every protocol it's assigned on. - a service name —
https,ssh,mysql— returns every port whose service name contains that text. - a keyword from the description —
secure shell,web server,name server.
- a port number —
- Filter by protocol to narrow results to TCP, UDP, SCTP, or DCCP.
- Filter by port range to restrict to Well-Known (0–1023) or Registered (1024–49151) ports.
Results appear as a table showing the port, protocol, service name, description, and range classification. You can copy the table or download it as a CSV. Leave the search box empty to browse the registry with just the protocol and range filters applied.
What are the port ranges?
The IANA divides port numbers into three ranges:
- Well-Known (0–1023) — reserved for core, system-level services such as HTTP (80), HTTPS (443), SSH (22), and DNS (53). Binding to these typically requires elevated privileges.
- Registered (1024–49151) — assigned by IANA to specific applications on request, e.g. MySQL (3306) or RDP (3389).
- Dynamic / Private (49152–65535) — never assigned by IANA; used for ephemeral, client-side connections. These aren't listed here because they carry no service registrations.
Why does one port show several rows?
A single port number can be registered independently for different transport protocols (TCP, UDP, SCTP, DCCP), and occasionally under more than one service name. Each combination is its own row, so searching 80 returns the TCP, UDP, and SCTP registrations separately.
Common ports at a glance
| Port | Service | Protocol |
|---|---|---|
| 22 | SSH | TCP |
| 25 | SMTP | TCP |
| 53 | DNS | TCP/UDP |
| 80 | HTTP | TCP |
| 443 | HTTPS | TCP |
| 3306 | MySQL | TCP |
| 3389 | RDP | TCP |
Privacy
The entire port database is bundled with the tool and every search runs locally in your browser. Nothing you type is sent to a server.
Use it from code
From 3 credits per callREST API
curl -X POST https://api.iotools.cloud/v1/tool/port-lookup \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"search": "443",
"protocol": "all",
"portRange": "all"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `port-lookup` tool (Port Lookup) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.