Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-27

Expert(s)

  • TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, and Michael Scharf
  • SCTP: Michael Tuexen
  • DCCP: Eddie Kohler and Yoshifumi Nishida

Reference

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

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 basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

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

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.

Registration Forms

Available Formats

Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
filex-lport 1887 tcp FileX Listening Port Megan Woods Megan Woods
filex-lport 1887 udp FileX Listening Port Megan Woods Megan Woods
odi-port 3187 tcp Open Design Listen Port Phivos Aristides Phivos Aristides
odi-port 3187 udp Open Design Listen Port Phivos Aristides Phivos Aristides
listmgr-port 3767 tcp ListMGR Port Takashi Kubota Takashi Kubota 2003-06
listmgr-port 3767 udp ListMGR Port Takashi Kubota Takashi Kubota 2003-06
listcrt-port 3913 tcp ListCREATOR Port Tomokazu Asai Tomokazu Asai 2003-11
listcrt-port 3913 udp ListCREATOR Port Tomokazu Asai Tomokazu Asai 2003-11
listcrt-port-2 3914 tcp ListCREATOR Port 2 Tomokazu Asai Tomokazu Asai 2003-11
listcrt-port-2 3914 udp ListCREATOR Port 2 Tomokazu Asai Tomokazu Asai 2003-11
xmcp 4788 tcp eXtensible Messaging Client Protocol Cisco Glenn Matthews 2011-05-23 2011-10-25 Defined TXT keys: txtvers=1 (as described in the draft) protovers=<comma-separated list of major/minor versions supported> (examples: "protovers=1.0" "protovers=1.1,2.0"
octopustentacle 10933 tcp Listen port used by the Octopus Deploy Tentacle deployment agent Octopus Deploy Pty. Ltd. Paul Stovell 2015-01-28
inedo 46336 tcp Listen port used for Inedo agent communication Inedo Steve Dennis 2016-01-12
fix Financial Information Exchange (FIX) Protocol Joakim Johansson Joakim Johansson Defined TXT keys: Currently valid enumerated values: FIX Session Protocol Versions (SESSIONVERSION): 1.1 FIX Application Protocol Versions (APPLICATIONVERSION): 2.7, 3.0, 4.0, 4.1, 4.2, 4.3, 4.4, 5.0 Possible TXT records defined and their values (replace uppercase text with enumerations from the list above): txtvers=1 fix=APPLICATIONVERSION fix supported=APPLICATIONVERSION[,APPLICATIONVERSION, ... ,APPLICATIONVERSION] fixt=SESSIONVERSION
presence Peer-to-peer messaging / Link-Local Messaging XMPP Registrar XMPP Registrar Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html Note: Registration updated May 2007. Was formerly listed as "iChat AV" (Apple's IM client for Mac OS X) with TXT keys: txtvers, port.p2pj, phsh, vc, 1st, AIM, msg, status, last When first shipped in Mac OS X 10.2, iChat's peer-to-peer messaging protocol was created to solve the problem of serverless messaging between peers on the same link. However, there is nothing inherent in the protocol that limits it to being only link-local; it was simply an artifact of iChat in Mac OS X 10.2 using link-local Multicast DNS to discover peers. With the advent of Wide-Area DNS-SD, it is also possible to use iChat's peer-to-peer messaging between machines on different links.
rfbc Remote Frame Buffer Client (Used by VNC viewers in listen-mode) Ole-Morten Duesund Ole-Morten Duesund Defined TXT keys: server=dns-name/ip-address:port of currently displayed VNC server. Empty if not showing anything/available.

Contact Information

Name Organization Contact URI Last Updated
Cisco glenn.matthews&cisco.com 2011-10-25
Glenn Matthews glenn.matthews&cisco.com 2011-05-23
Inedo support&inedo.com 2016-01-12
Joakim Johansson joakim.johansson&tbricks.com
Megan Woods megan.woods&woods-gebler.com 2024-08-29
Ole-Morten Duesund ole-morten.duesund&bbvisuals.no
Octopus Deploy Pty. Ltd. paul&octopusdeploy.com 2015-01-28
Paul Stovell Octopus Deploy Pty. Ltd. paul&octopusdeploy.com 2015-01-28
Phivos Aristides phivos&opendesign.com
Steve Dennis sdennis&inedo.com 2016-01-12
Takashi Kubota kubota.takashi&pfu.fugitsu.com 2003-06
Tomokazu Asai asai.tomokazu&pfu.fujitsu.com 2003-11
XMPP Registrar registrar&xmpp.org