Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-15

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
efs 520 tcp extended file name server
router 520 udp local routing process (on site); uses variant of Xerox NS routing information protocol - RIP
atm-zip-office 1520 tcp atm zip office Wilson Kwan Wilson Kwan
atm-zip-office 1520 udp atm zip office Wilson Kwan Wilson Kwan
pvsw 2520 tcp Pervasive Listener Chuck Talk Chuck Talk
pvsw 2520 udp Pervasive Listener Chuck Talk Chuck Talk
galileolog 3520 tcp Netvion Galileo Log Port Ray Caruso Ray Caruso 2002-06
galileolog 3520 udp Netvion Galileo Log Port Ray Caruso Ray Caruso 2002-06
targus-getdata 5200 tcp TARGUS GetData John Keaveney John Keaveney
targus-getdata 5200 udp TARGUS GetData John Keaveney John Keaveney
targus-getdata1 5201 tcp TARGUS GetData 1 John Keaveney John Keaveney
targus-getdata1 5201 udp TARGUS GetData 1 John Keaveney John Keaveney
targus-getdata2 5202 tcp TARGUS GetData 2 John Keaveney John Keaveney
targus-getdata2 5202 udp TARGUS GetData 2 John Keaveney John Keaveney
targus-getdata3 5203 tcp TARGUS GetData 3 John Keaveney John Keaveney
targus-getdata3 5203 udp TARGUS GetData 3 John Keaveney John Keaveney
5204-5208 Unassigned
nomad 5209 tcp Nomad Device Video Transfer Morega Systems Inc. Ashraf Tahir 2012-08-20
5209 udp Reserved

Contact Information

Name Organization Contact URI Last Updated
Ashraf Tahir Morega Systems Inc. atahir&morega.com 2012-08-20
Chuck Talk ctalk&pervasive.com
John Keaveney johnkeaveney&targusinfo.com
Morega Systems Inc. atahir&morega.com 2012-08-20
Ray Caruso ray.caruso&netvion.com 2002-06
Wilson Kwan wilsonk%25toronto@zip.atm.com