Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-11-10

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
rescap 283 tcp rescap Paul Hoffman Paul Hoffman
rescap 283 udp rescap Paul Hoffman Paul Hoffman
productinfo 1283 tcp Product Information
productinfo 1283 udp Product Information
lnvstatus 2283 tcp LNVSTATUS
lnvstatus 2283 udp LNVSTATUS
silkp2 2830 tcp silkp2
silkp2 2830 udp silkp2
silkp3 2831 tcp silkp3
silkp3 2831 udp silkp3
silkp4 2832 tcp silkp4 Erik Skyten Erik Skyten
silkp4 2832 udp silkp4 Erik Skyten Erik Skyten
glishd 2833 tcp glishd Darrell Schiebel Darrell Schiebel
glishd 2833 udp glishd Darrell Schiebel Darrell Schiebel
evtp 2834 tcp EVTP
evtp 2834 udp EVTP
evtp-data 2835 tcp EVTP-DATA Eric Bruno Eric Bruno
evtp-data 2835 udp EVTP-DATA Eric Bruno Eric Bruno
catalyst 2836 tcp catalyst Garret Tollkuhn Garret Tollkuhn
catalyst 2836 udp catalyst Garret Tollkuhn Garret Tollkuhn
repliweb 2837 tcp Repliweb William Orme William Orme
repliweb 2837 udp Repliweb William Orme William Orme
starbot 2838 tcp Starbot Markus Sabadello Markus Sabadello
starbot 2838 udp Starbot Markus Sabadello Markus Sabadello
nmsigport 2839 tcp NMSigPort Peter Egli Peter Egli
nmsigport 2839 udp NMSigPort Peter Egli Peter Egli
net-assistant 3283 tcp Net Assistant Michael Stein Michael Stein 2025-01-23
net-assistant 3283 udp Net Assistant Michael Stein Michael Stein 2025-01-23
5283-5297 Unassigned
genstat 7283 tcp General Statistics Rendezvous Protocol VSN International Ltd. Sean D. Sollé 2011-09-28
7283 udp Reserved
8283-8291 Unassigned
callwaveiam 9283 tcp CallWaveIAM Colin Kelley Colin Kelley
callwaveiam 9283 udp CallWaveIAM Colin Kelley Colin Kelley
keysrvr 19283 tcp Key Server for SASSAFRAS Mark Valence Mark Valence
keysrvr 19283 udp Key Server for SASSAFRAS Mark Valence Mark Valence

Contact Information

Name Organization Contact URI Last Updated
Colin Kelley cdk&callwave.com
Darrell Schiebel dschieb&cv.nrao.edu
Eric Bruno ebruno&solution-soft.com
Erik Skyten eki&silknet.com
Garret Tollkuhn garret&multiviewgroup.com
Mark Valence kurash&sassafras.com
Markus Sabadello sabadello&starbot.org
Michael Stein mvs&apple.com
Paul Hoffman phoffman&proper.com 2024-07-23
Peter Egli peter.egli&mail.inalp.com
Sean D. Sollé VSN International Ltd. sean&vsni.co.uk 2011-09-28
VSN International Ltd. sean&vsni.co.uk 2011-09-28
William Orme bill&repliweb.com