Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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
- [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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| snare | 509 | tcp | snare | [Dennis_Batchelder] | [Dennis_Batchelder] | ||||||
| snare | 509 | udp | snare | [Dennis_Batchelder] | [Dennis_Batchelder] | ||||||
| robcad-lm | 1509 | tcp | Robcad, Ltd. License Manager | [Hindin_Joseph] | [Hindin_Joseph] | ||||||
| robcad-lm | 1509 | udp | Robcad, Ltd. License Manager | [Hindin_Joseph] | [Hindin_Joseph] | ||||||
| fjmpss | 2509 | tcp | fjmpss | [Makoto_Watanabe] | [Makoto_Watanabe] | ||||||
| fjmpss | 2509 | udp | fjmpss | [Makoto_Watanabe] | [Makoto_Watanabe] | ||||||
| vt-ssl | 3509 | tcp | Virtual Token SSL Port | [Libor_Sykora] | [Libor_Sykora] | 2002-05 | |||||
| vt-ssl | 3509 | udp | Virtual Token SSL Port | [Libor_Sykora] | [Libor_Sykora] | 2002-05 | |||||
| car | 5090 | sctp | Candidate AR | ||||||||
| cxtp | 5091 | sctp | Context Transfer Protocol | 2005-07 | [RFC4065] | ||||||
| 5092 | tcp | Reserved | |||||||||
| magpie | 5092 | udp | Magpie Binary | [Phil_Maker] | [Phil_Maker] | 2008-06-18 | |||||
| sentinel-lm | 5093 | tcp | Sentinel LM | [Derick_Snyder] | [Derick_Snyder] | ||||||
| sentinel-lm | 5093 | udp | Sentinel LM | [Derick_Snyder] | [Derick_Snyder] | ||||||
| hart-ip | 5094 | tcp | HART-IP | [Wally_Pratt_Jr] | [Wally_Pratt_Jr] | 2010-03-02 | |||||
| hart-ip | 5094 | udp | HART-IP | [Wally_Pratt_Jr] | [Wally_Pratt_Jr] | 2010-03-02 | |||||
| 5095-5098 | Unassigned | ||||||||||
| sentlm-srv2srv | 5099 | tcp | SentLM Srv2Srv | [Derick_Snyder] | [Derick_Snyder] | ||||||
| sentlm-srv2srv | 5099 | udp | SentLM Srv2Srv | [Derick_Snyder] | [Derick_Snyder] | ||||||
| spramsca | 5769 | tcp | x509solutions Internal CA | [Brendan_Fay] | [Brendan_Fay] | 2006-02 | |||||
| spramsca | 5769 | udp | x509solutions Internal CA | [Brendan_Fay] | [Brendan_Fay] | 2006-02 | |||||
| spramsd | 5770 | tcp | x509solutions Secure Data | [Brendan_Fay] | [Brendan_Fay] | 2006-02 | |||||
| spramsd | 5770 | udp | x509solutions Secure Data | [Brendan_Fay] | [Brendan_Fay] | 2006-02 | |||||
| mgcs-mfp-port | 6509 | tcp | MGCS-MFP Port | [Minoru_Ozaki] | [Minoru_Ozaki] | ||||||
| mgcs-mfp-port | 6509 | udp | MGCS-MFP Port | [Minoru_Ozaki] | [Minoru_Ozaki] | ||||||
| acplt | 7509 | tcp | ACPLT - process automation service | [Chair_for_Process_Control_Engineering] | [Ulrich_Epple] | 2010-12-07 | 2012-08-07 | ||||
| 7509 | udp | Reserved | |||||||||
| kca-service | 9878 | udp | The KX509 Kerberized Certificate Issuance Protocol in Use in 2012 | [IESG] | [IETF_Chair] | 2012-07-12 | [RFC6717] | Historically, this service has been referred to as "kca_service", but this service name does not meet the registry requirements. | |||
| xoms | 16619 | tcp | X509 Objects Management Service | [Francis_GASCHET] | [Francis_GASCHET] | 2008-09-08 | |||||
| 25010-25099 | Unassigned | ||||||||||
| 35007-35099 | Unassigned | ||||||||||
| candrp | 42509 | tcp | CA discovery response | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
| candrp | 42509 | udp | CA discovery response | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
| certificates | tcp | Server for S/MIME and PGP certificates | [IESG] | [John_Levine] | 2016-07-26 | [draft-bhjl-x509-srv-01] | Defined TXT keys: None | ||||
| smimeca | tcp | Domain signing certificate for S/MIME keys | [IESG] | [John_Levine] | 2016-07-26 | [draft-bhjl-x509-srv-01] | Defined TXT keys: None |