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
2674 UDP ewnn ewnn Yasunari Yamashita Assigned
2675 TCP ttc-etap TTC ETAP Daniel Becker Assigned
2675 UDP ttc-etap TTC ETAP Daniel Becker Assigned
2676 TCP simslink SIMSLink Steve Ryckman Assigned
2676 UDP simslink SIMSLink Steve Ryckman Assigned
2677 TCP gadgetgate1way Gadget Gate 1 Way Assigned
2677 UDP gadgetgate1way Gadget Gate 1 Way Assigned
2678 TCP gadgetgate2way Gadget Gate 2 Way Matt Rollins Assigned
2678 UDP gadgetgate2way Gadget Gate 2 Way Matt Rollins Assigned
2679 TCP syncserverssl Sync Server SSL Shawn Casey Assigned
2679 UDP syncserverssl Sync Server SSL Shawn Casey Assigned
2680 TCP pxc-sapxom pxc-sapxom Hideki Kiriyama Assigned
2680 UDP pxc-sapxom pxc-sapxom Hideki Kiriyama Assigned
2681 TCP mpnjsomb mpnjsomb Takenori Miyahara Assigned
2681 UDP mpnjsomb mpnjsomb Takenori Miyahara Assigned
2682 Not specified Removed Deprecated or removed
2683 TCP ncdloadbalance NCDLoadBalance Tim Stevenson Assigned
2683 UDP ncdloadbalance NCDLoadBalance Tim Stevenson Assigned
2684 TCP mpnjsosv mpnjsosv Assigned
2684 UDP mpnjsosv mpnjsosv Assigned
2685 TCP mpnjsocl mpnjsocl Assigned
2685 UDP mpnjsocl mpnjsocl Assigned
2686 TCP mpnjsomg mpnjsomg Takenori Miyahara Assigned
2686 UDP mpnjsomg mpnjsomg Takenori Miyahara Assigned
2687 TCP pq-lic-mgmt pq-lic-mgmt Bob Sledge Assigned
2687 UDP pq-lic-mgmt pq-lic-mgmt Bob Sledge Assigned
2688 TCP md-cg-http md-cf-http Lyndon Nerenberg Assigned
2688 UDP md-cg-http md-cf-http Lyndon Nerenberg Assigned
2689 TCP fastlynx FastLynx Dave Sewell Assigned
2689 UDP fastlynx FastLynx Dave Sewell Assigned
2690 TCP hp-nnm-data HP NNM Embedded Database Chris Das Assigned
2690 UDP hp-nnm-data HP NNM Embedded Database Chris Das Assigned
2691 TCP itinternet ITInternet ISM Server Ron Ehli Assigned
2691 UDP itinternet ITInternet ISM Server Ron Ehli Assigned
2692 TCP admins-lms Admins LMS Dagfinn Saether Assigned
2692 UDP admins-lms Admins LMS Dagfinn Saether Assigned
2693 TCP Unassigned Unassigned
2693 UDP Unassigned Unassigned
2694 TCP pwrsevent pwrsevent Yoshinobu Nakamura Assigned
2694 UDP pwrsevent pwrsevent Yoshinobu Nakamura Assigned
2695 TCP vspread VSPREAD Sumitake kobayashi Assigned
2695 UDP vspread VSPREAD Sumitake kobayashi Assigned
2696 TCP unifyadmin Unify Admin Daegis, Inc. Assigned
2696 UDP unifyadmin Unify Admin Daegis, Inc. Assigned
2697 TCP oce-snmp-trap Oce SNMP Trap Port Peter Teeuwen Assigned
2697 UDP oce-snmp-trap Oce SNMP Trap Port Peter Teeuwen Assigned
2698 TCP mck-ivpip MCK-IVPIP Robert Vincent Assigned
2698 UDP mck-ivpip MCK-IVPIP Robert Vincent Assigned
2699 TCP csoft-plusclnt Csoft Plus Client Nedelcho Stanev Assigned
2699 UDP csoft-plusclnt Csoft Plus Client Nedelcho Stanev 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 ↗