Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-03-18
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, 
Jana Iyengar, and Michael Scharf
SCTP: Michael Tuexen
DCCP: Eddie Kohler and Yoshifumi Nishida
Reference
[RFC6335]
Note
Service names and port numbers are used to distinguish between different
services that run over transport protocols such as TCP, UDP, DCCP, and
SCTP.

Service names are assigned on a first-come, first-served process, as
documented in [RFC6335].

Port numbers are assigned in various ways, based on three ranges: System
Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private
Ports (49152-65535); the different uses of these ranges are described in
[RFC6335]. According to Section 8.1.2 of [RFC6335], System Ports are 
assigned by the "IETF Review" or "IESG Approval" procedures described in 
[RFC8126]. User Ports are assigned by IANA using the "IETF Review" process, 
the "IESG Approval" process, or the "Expert Review" process, as per 
[RFC6335]. Dynamic Ports are not assigned.

The registration procedures for service names and port numbers are
described in [RFC6335].

Assigned ports both System and User ports SHOULD NOT be used without
or prior to IANA registration.

************************************************************************
* PLEASE NOTE THE FOLLOWING:                                           *
*                                                                      *
* ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN             *
* ENDORSEMENT OF AN APPLICATION OR PRODUCT, AND THE FACT THAT NETWORK  *
* TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT   *
* IT IS "GOOD" TRAFFIC, NOR THAT IT NECESSARILY CORRESPONDS TO THE     *
* ASSIGNED SERVICE. FIREWALL AND SYSTEM ADMINISTRATORS SHOULD          *
* CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF    *
* THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER          *
* REGISTERED OR NOT.                                                   *
************************************************************************

Request an Assignment
  [https://www.iana.org/protocols/apply]

Available Formats

CSV

XML

HTML

Plain text
Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
http-alt 591 tcp FileMaker, Inc. - HTTP Alternate (see Port 80) [Clay_Maeckel] [Clay_Maeckel]
http-alt 591 udp FileMaker, Inc. - HTTP Alternate (see Port 80) [Clay_Maeckel] [Clay_Maeckel]
fmpro-fdal 2399 tcp FileMaker, Inc. - Data Access Layer [Clay_Maeckel] [Clay_Maeckel]
fmpro-fdal 2399 udp FileMaker, Inc. - Data Access Layer [Clay_Maeckel] [Clay_Maeckel]
fmpro-internal 5003 tcp FileMaker, Inc. - Proprietary transport [Clay_Maeckel] [Clay_Maeckel]
fmpro-internal 5003 udp FileMaker, Inc. - Proprietary name binding [Clay_Maeckel] [Clay_Maeckel]
fmpro-v6 5013 tcp FileMaker, Inc. - Proprietary transport [Alex_Chen] [Alex_Chen] 2007-08-01
fmpro-v6 5013 udp FileMaker, Inc. - Proprietary transport [Alex_Chen] [Alex_Chen] 2007-08-01
fmwp 5015 tcp FileMaker, Inc. - Web publishing [Alex_Chen] [Alex_Chen] 2009-11-25
jwpc 16020 tcp Filemaker Java Web Publishing Core [Robert_Parks] [Robert_Parks] 2010-05-12
jwpc-bin 16021 tcp Filemaker Java Web Publishing Core Binary [Robert_Parks] [Robert_Parks] 2010-05-12
fmserver-admin FileMaker Server Administration Communication Service [Eric_Jacobson] [Eric_Jacobson] Defined TXT keys: None

Contact Information

ID Name Contact URI Last Updated
[Alex_Chen] Alex Chen mailto:alex_chen&filemaker.com 2009-11-25
[Clay_Maeckel] Clay Maeckel mailto:clay&claris.com 2023-09-12
[Eric_Jacobson] Eric Jacobson mailto:eric_jacobson&filemaker.com
[Robert_Parks] Robert Parks mailto:robert_parks&filemaker.com 2010-05-12