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
2947 TCP gpsd GPS Daemon request/response protocol Eric S. Raymond Assigned
2947 UDP gpsd GPS Daemon request/response protocol Eric S. Raymond Assigned
2948 TCP wap-push WAP PUSH Assigned
2948 UDP wap-push WAP PUSH Assigned
2949 TCP wap-pushsecure WAP PUSH SECURE WAP Forum Assigned
2949 UDP wap-pushsecure WAP PUSH SECURE WAP Forum Assigned
2950 TCP esip ESIP David Stephenson Assigned
2950 UDP esip ESIP David Stephenson Assigned
2951 TCP ottp OTTP Brent Foster Assigned
2951 UDP ottp OTTP Brent Foster Assigned
2952 TCP mpfwsas MPFWSAS Toru Murai Assigned
2952 UDP mpfwsas MPFWSAS Toru Murai Assigned
2953 TCP ovalarmsrv OVALARMSRV Assigned
2953 UDP ovalarmsrv OVALARMSRV Assigned
2954 TCP ovalarmsrv-cmd OVALARMSRV-CMD Eric Pulsipher Assigned
2954 UDP ovalarmsrv-cmd OVALARMSRV-CMD Eric Pulsipher Assigned
2955 TCP csnotify CSNOTIFY Israel Beniaminy Assigned
2955 UDP csnotify CSNOTIFY Israel Beniaminy Assigned
2956 TCP ovrimosdbman OVRIMOSDBMAN Dimitrios Souflis Assigned
2956 UDP ovrimosdbman OVRIMOSDBMAN Dimitrios Souflis Assigned
2957 TCP jmact5 JAMCT5 Assigned
2957 UDP jmact5 JAMCT5 Assigned
2958 TCP jmact6 JAMCT6 Assigned
2958 UDP jmact6 JAMCT6 Assigned
2959 TCP rmopagt RMOPAGT Shuji Okubo Assigned
2959 UDP rmopagt RMOPAGT Shuji Okubo Assigned
2960 TCP dfoxserver DFOXSERVER David Holden Assigned
2960 UDP dfoxserver DFOXSERVER David Holden Assigned
2961 TCP boldsoft-lm BOLDSOFT-LM Fredrik Haglund Assigned
2961 UDP boldsoft-lm BOLDSOFT-LM Fredrik Haglund Assigned
2962 TCP iph-policy-cli IPH-POLICY-CLI Assigned
2962 UDP iph-policy-cli IPH-POLICY-CLI Assigned
2963 TCP iph-policy-adm IPH-POLICY-ADM Shai Herzog Assigned
2963 UDP iph-policy-adm IPH-POLICY-ADM Shai Herzog Assigned
2964 TCP bullant-srap BULLANT SRAP Assigned
2964 UDP bullant-srap BULLANT SRAP Assigned
2965 TCP bullant-rap BULLANT RAP Michael Cahill Assigned
2965 UDP bullant-rap BULLANT RAP Michael Cahill Assigned
2966 TCP idp-infotrieve IDP-INFOTRIEVE Kevin Bruckert Assigned
2966 UDP idp-infotrieve IDP-INFOTRIEVE Kevin Bruckert Assigned
2967 TCP ssc-agent SSC-AGENT George Dzieciol Assigned
2967 UDP ssc-agent SSC-AGENT George Dzieciol Assigned
2968 TCP enpp ENPP Kazuhito Gassho Assigned
2968 UDP enpp ENPP Kazuhito Gassho Assigned
2969 TCP essp ESSP Hitoshi Ishida Assigned
2969 UDP essp ESSP Hitoshi Ishida Assigned
2970 TCP index-net INDEX-NET Chris J. Wren Assigned
2970 UDP index-net INDEX-NET Chris J. Wren Assigned
2971 TCP netclip NetClip clipboard daemon Rudi Chiarito Assigned
2971 UDP netclip NetClip clipboard daemon Rudi Chiarito 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 ↗