Networking reference

TCP & UDP Port Numbers – Service & Protocol Lookup

Search the complete IANA service-name and port-number registry by port, protocol, service, assignee or RFC, including TCP, UDP, SCTP, DCCP and unqualified entries.

Search this dataset

Use exact codes, names or any declared searchable field.

TCP & UDP Port Numbers – Service & Protocol LookupShowing 50 of 14,533 records
PortProtocolServiceDescriptionAssigneeRegistration dateReference/RFCStatusRecord details
3184 UDP apogeex-port ApogeeX Port Tom Nys Assigned
3185 TCP smpppd SuSE Meta PPPD Arvin Schnell Assigned
3185 UDP smpppd SuSE Meta PPPD Arvin Schnell Assigned
3186 TCP iiw-port IIW Monitor User Port Corey Burnett Assigned
3186 UDP iiw-port IIW Monitor User Port Corey Burnett Assigned
3187 TCP odi-port Open Design Listen Port Phivos Aristides Assigned
3187 UDP odi-port Open Design Listen Port Phivos Aristides Assigned
3188 TCP brcm-comm-port Broadcom Port Thomas L. Johnson Assigned
3188 UDP brcm-comm-port Broadcom Port Thomas L. Johnson Assigned
3189 TCP pcle-infex Pinnacle Sys InfEx Port Anthon van der Neut Assigned
3189 UDP pcle-infex Pinnacle Sys InfEx Port Anthon van der Neut Assigned
3190 TCP csvr-proxy ConServR Proxy Assigned
3190 UDP csvr-proxy ConServR Proxy Assigned
3191 TCP csvr-sslproxy ConServR SSL Proxy Mikhail Kruk Assigned
3191 UDP csvr-sslproxy ConServR SSL Proxy Mikhail Kruk Assigned
3192 TCP firemonrcc FireMon Revision Control Michael Bishop Assigned
3192 UDP firemonrcc FireMon Revision Control Michael Bishop Assigned
3193 TCP spandataport SpanDataPort Jesse McKay Assigned
3193 UDP spandataport SpanDataPort Jesse McKay Assigned
3194 TCP magbind Rockstorm MAG protocol Jens Nilsson Assigned
3194 UDP magbind Rockstorm MAG protocol Jens Nilsson Assigned
3195 TCP ncu-1 Network Control Unit Assigned
3195 UDP ncu-1 Network Control Unit Assigned
3196 TCP ncu-2 Network Control Unit Charlie Hundre Assigned
3196 UDP ncu-2 Network Control Unit Charlie Hundre Assigned
3197 TCP embrace-dp-s Embrace Device Protocol Server Assigned
3197 UDP embrace-dp-s Embrace Device Protocol Server Assigned
3198 TCP embrace-dp-c Embrace Device Protocol Client Elliot Schwartz Assigned
3198 UDP embrace-dp-c Embrace Device Protocol Client Elliot Schwartz Assigned
3199 TCP dmod-workspace DMOD WorkSpace Nick Plante Assigned
3199 UDP dmod-workspace DMOD WorkSpace Nick Plante Assigned
3200 TCP tick-port Press-sense Tick Port Boris Svetlitsky Assigned
3200 UDP tick-port Press-sense Tick Port Boris Svetlitsky Assigned
3201 TCP cpq-tasksmart CPQ-TaskSmart Jackie Lau Assigned
3201 UDP cpq-tasksmart CPQ-TaskSmart Jackie Lau Assigned
3202 TCP intraintra IntraIntra Matthew Asham Assigned
3202 UDP intraintra IntraIntra Matthew Asham Assigned
3203 TCP netwatcher-mon Network Watcher Monitor Assigned
3203 UDP netwatcher-mon Network Watcher Monitor Assigned
3204 TCP netwatcher-db Network Watcher DB Access Hirokazu Fujisawa Assigned
3204 UDP netwatcher-db Network Watcher DB Access Hirokazu Fujisawa Assigned
3205 TCP isns iSNS Server Port [RFC4171] Assigned
3205 UDP isns iSNS Server Port [RFC4171] Assigned
3206 TCP ironmail IronMail POP Proxy Mike Hudack Assigned
3206 UDP ironmail IronMail POP Proxy Mike Hudack Assigned
3207 TCP vx-auth-port Veritas Authentication Port Senthil Ponnuswamy Assigned
3207 UDP vx-auth-port Veritas Authentication Port Senthil Ponnuswamy Assigned
3208 TCP pfu-prcallback PFU PR Callback Tetsuharu Hanada Assigned
3208 UDP pfu-prcallback PFU PR Callback Tetsuharu Hanada Assigned
3209 TCP netwkpathengine HP OpenView Network Path Engine Server Anthony Walker Assigned

Look up a port number, service name, transport protocol, assignee or RFC in IANA's current registry. The table keeps every row in the 17 August 2026 snapshot, so one port can appear more than once when it has separate TCP, UDP or other registrations.

How to use the port lookup

Enter a number such as 22, 53, 80, 443, 3306 or 8080 to find exact registrations and any registered range containing that port. You can also search for a service such as ssh or mysql, a protocol, an assignee, or reference text such as RFC9110. Use the Protocol and Status filters when a search returns several rows.

Blank values mean the source registry does not provide that field. They have not been guessed. Assignee identifiers are resolved against the people and organisations directory in IANA's XML registry where a readable name is available.

Port ranges and status labels

  • System ports: 0–1023. These are also commonly called well-known ports.
  • User ports: 1024–49151. IANA can register services in this range.
  • Dynamic or private ports: 49152–65535. IANA does not assign services from this range.

Status is a page-level label derived from the source row. Reserved and Unassigned follow IANA's description. Rows whose source text identifies a de-registration or removal are labelled Deprecated or removed. A row with a service name but no port is labelled Service name only. All other rows are labelled Assigned.

Why the same port can have several entries

TCP and UDP are different transport protocols, so the same number can be registered for both without representing the same network conversation. The registry also includes SCTP, DCCP, aliases, historic records and registrations without a specified transport protocol. They remain in this database so the source is not reduced to a hand-picked list.

Common port questions

What service normally uses port 22?

IANA registers ssh on port 22 for TCP and UDP, with an additional SCTP registration. In everyday networks, TCP port 22 is the familiar SSH remote-access service.

Why does port 53 show TCP and UDP?

The domain service is registered on port 53 for both TCP and UDP. DNS software chooses the transport according to the operation and response requirements.

What is the difference between ports 80 and 443?

IANA associates port 80 with HTTP-related service names and port 443 with HTTPS. A registration describes the conventional use; it does not inspect or guarantee the traffic running there.

What uses port 3306?

The registry lists mysql on port 3306 for TCP and UDP. MySQL client connections are ordinarily associated with TCP, but this page retains both official registry rows.

Is port 8080 always an HTTP proxy?

No. IANA registers http-alt on port 8080 for TCP and UDP, but applications can use ports differently. Identify the listening process and configuration before drawing a security conclusion.

Should I open a port because it is registered here?

No. Open only the ports required by a known application and restrict source networks where possible. A registry entry is not a firewall recommendation.

IANA updates the registry as assignments change. Use Report incorrect data if this snapshot no longer matches the official record, and include the IANA or RFC link so the change can be verified.

Provenance

Data sources

Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Primary officialVisit source ↗
Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry (CSV)

Primary officialVisit source ↗
Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry (XML)

Primary officialVisit source ↗
Internet Engineering Task Force

RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

Primary standardVisit source ↗
Internet Engineering Task Force

RFC 7605: Recommendations on Using Assigned Transport Port Numbers

Primary standardVisit source ↗
Internet Assigned Numbers Authority

Licensing Terms

Primary officialVisit source ↗