Networking reference
TCP & UDP Port Numbers – Service & Protocol Lookup
Search the complete IANA service-name and port-number registry by port, protocol, service, assignee or RFC, including TCP, UDP, SCTP, DCCP and unqualified entries.
| Port | Protocol | Service | Description | Assignee | Registration date | Reference/RFC | Status | Record details |
|---|---|---|---|---|---|---|---|---|
| — | Not specified | shoppersync | SplashShopper Synchronization Service | Justin Cepelak | — | — | Service name only | → |
| — | UDP | shots-sync | The protocol is used to sync database among iOS devices and Mac OS X computers. | Ryota Kurata | 2016-02-10 | — | Service name only | → |
| — | Not specified | shoutcast | Nicecast | Rogue Amoeba | — | — | Service name only | → |
| — | TCP | siminsufflator | Simulated insufflator synchronisation protocol | Niels Castle | 2014-06-18 | — | Service name only | → |
| — | Not specified | simmon | Medical simulation patient monitor syncronisation protocol | Niels Castle | — | — | Service name only | → |
| — | Not specified | simusoftpong | simusoftpong iPhone game protocol | Anders Svensson | — | — | Service name only | → |
| — | Not specified | sipuri | Session Initiation Protocol Uniform Resource Identifier | Jae Woo Lee | — | — | Service name only | → |
| — | Not specified | sironaxray | Sirona Xray Protocol | Michael Dalpiaz | — | — | Service name only | → |
| — | TCP | skillscapture | The protocol is used to transfer database records between an iOS device to a Mac OS X computer | Legentis Ltd | 2013-07-01 | — | Service name only | → |
| — | UDP | skillscapture | The protocol is used to transfer database records between an iOS device to a Mac OS X computer | Legentis Ltd | 2013-07-01 | — | Service name only | → |
| — | Not specified | skype | Skype | — | — | — | Service name only | → |
| — | UDP | sleep-proxy | Sleep Proxy Server | Stuart Cheshire; Marc Krochmal | — | — | Service name only | → |
| — | TCP | sleeptracker | Sleeptracker(R) The loT Smartbed Platform | Fullpower Technologies, Inc. | 2016-08-17 | — | Service name only | → |
| — | Not specified | slimcli | SliMP3 Server Command-Line Interface | Dean Blackketter | — | — | Service name only | → |
| — | Not specified | slimhttp | SliMP3 Server Web Interface | Dean Blackketter | — | — | Service name only | → |
| — | TCP | slpda | Remote Service Discovery in the Service Location | — | — | [RFC3832] | Service name only | → |
| — | UDP | slpda | Remote Service Discovery in the Service Location | — | — | [RFC3832] | Service name only | → |
| — | TCP | smag | terminal access to laundry appliances | Schulthess Maschinen AG | 2018-11-30 | — | Service name only | → |
| — | TCP | smaho | Smart Home Device Setup | SMAHO | 2021-11-15 | — | Service name only | → |
| — | Not specified | smartenergy | Smart Energy Profile | Robby Simpson, PhD | — | — | Service name only | → |
| — | TCP | smartsocket | home control | Robert Diamond | 2012-07-06 | — | Service name only | → |
| — | Not specified | smb | Server Message Block over TCP/IP | — | — | — | Service name only | → |
| — | TCP | smimeca | Domain signing certificate for S/MIME keys | IESG | 2016-07-26 | [draft-bhjl-x509-srv-01] | Service name only | → |
| — | Not specified | sms | Short Text Message Sending and Delivery Status Service | Christian Flintrup | — | — | Service name only | → |
| — | Not specified | smsync | Syncellence file synchronization protocol | Dialectro Software | 2011-10-20 | — | Service name only | → |
| — | TCP | snif-cln | SNIF End-to-End TLS Relay Client Connection | VESvault Corp | 2021-12-15 | [draft-zubov-snif-05, Section 4.5] | Service name only | → |
| — | TCP | snif-fifo | SNIF End-to-End TLS Relay Cluster | VESvault Corp | 2021-12-15 | [draft-zubov-snif-05, Section 4.6] | Service name only | → |
| — | TCP | snif-srv | SNIF End-to-End TLS Relay Service Connection | VESvault Corp | 2021-12-29 | [draft-zubov-snif-05, Section 4.3] | Service name only | → |
| — | Not specified | soap | Simple Object Access Protocol | Andrew Donoho | — | — | Service name only | → |
| — | Not specified | socketcloud | Socketcloud distributed application framework | Robert Goodyear | — | — | Service name only | → |
| — | TCP | soda | Secure On Device API | Smith Micro Software, Inc. | 2011-10-10 | — | Service name only | → |
| — | Not specified | souschef | SousChef Recipe Sharing Protocol | Ben | — | — | Service name only | → |
| — | Not specified | sox | Simple Object eXchange | Igor Mozolevsky | — | — | Service name only | → |
| — | Not specified | sparechange | SpareChange data sharing protocol | Dave Carrigan | — | — | Service name only | → |
| — | Not specified | sparql | SPARQL Protocol and RDF Query Language | Alex Tucker | — | — | Service name only | → |
| — | Not specified | spearcat | sPearCat Host Discovery | Pierre Frisch | — | — | Service name only | → |
| — | TCP | spidap | Sierra Photonics Inc. data protocol | Sierra Photonics, Inc. | 2011-10-20 | — | Service name only | → |
| — | Not specified | spincrisis | Spin Crisis | Sphera Software | — | — | Service name only | → |
| — | TCP | spiderelectron | Binary message passing protocol | Spider Electron | 2015-02-05 | — | Service name only | → |
| — | Not specified | spl-itunes | launchTunes | David Nanian | — | — | Service name only | → |
| — | Not specified | spr-itunes | netTunes | David Nanian | — | — | Service name only | → |
| — | Not specified | splashsync | SplashData Synchronization Service | Justin Cepelak | — | — | Service name only | → |
| — | TCP | split-dns64 | DNS64 in split configuration | Kasper Dupont | 2021-10-19 | — | Service name only | → |
| — | TCP | spres | SongPresenter | Tobias Hoffmann | 2012-10-09 | — | Service name only | → |
| — | TCP | spx-hmp | SpinetiX HMP | SpinetiX S.A. | 2011-10-18 | — | Service name only | → |
| — | TCP | sqp | Square Connect Control Protocol | Square Connect, Inc. | 2011-10-07 | — | Service name only | → |
| — | TCP | ss-sign | Samsung Smart Interaction for Group Network | Samsung | 2013-01-03 | — | Service name only | → |
| — | UDP | ss-sign-disc | Samsung Smart Interaction for Group Network Discovery | Samsung | 2013-01-03 | — | Service name only | → |
| — | TCP | ssd-audio | Studio Six Digital Wireless Audio | Studio Six Digital LLC | 2018-10-26 | — | Service name only | → |
| — | TCP | ssh | SSH Remote Login Protocol | Tatu Ylonen | — | — | Service name only | → |
Look up a port number, service name, transport protocol, assignee or RFC in IANA's current registry. The table keeps every row in the 17 August 2026 snapshot, so one port can appear more than once when it has separate TCP, UDP or other registrations.
How to use the port lookup
Enter a number such as 22, 53, 80, 443, 3306 or 8080 to find exact registrations and any registered range containing that port. You can also search for a service such as ssh or mysql, a protocol, an assignee, or reference text such as RFC9110. Use the Protocol and Status filters when a search returns several rows.
Blank values mean the source registry does not provide that field. They have not been guessed. Assignee identifiers are resolved against the people and organisations directory in IANA's XML registry where a readable name is available.
Port ranges and status labels
- System ports: 0–1023. These are also commonly called well-known ports.
- User ports: 1024–49151. IANA can register services in this range.
- Dynamic or private ports: 49152–65535. IANA does not assign services from this range.
Status is a page-level label derived from the source row. Reserved and Unassigned follow IANA's description. Rows whose source text identifies a de-registration or removal are labelled Deprecated or removed. A row with a service name but no port is labelled Service name only. All other rows are labelled Assigned.
Why the same port can have several entries
TCP and UDP are different transport protocols, so the same number can be registered for both without representing the same network conversation. The registry also includes SCTP, DCCP, aliases, historic records and registrations without a specified transport protocol. They remain in this database so the source is not reduced to a hand-picked list.
Common port questions
What service normally uses port 22?
IANA registers ssh on port 22 for TCP and UDP, with an additional SCTP registration. In everyday networks, TCP port 22 is the familiar SSH remote-access service.
Why does port 53 show TCP and UDP?
The domain service is registered on port 53 for both TCP and UDP. DNS software chooses the transport according to the operation and response requirements.
What is the difference between ports 80 and 443?
IANA associates port 80 with HTTP-related service names and port 443 with HTTPS. A registration describes the conventional use; it does not inspect or guarantee the traffic running there.
What uses port 3306?
The registry lists mysql on port 3306 for TCP and UDP. MySQL client connections are ordinarily associated with TCP, but this page retains both official registry rows.
Is port 8080 always an HTTP proxy?
No. IANA registers http-alt on port 8080 for TCP and UDP, but applications can use ports differently. Identify the listening process and configuration before drawing a security conclusion.
Should I open a port because it is registered here?
No. Open only the ports required by a known application and restrict source networks where possible. A registry entry is not a firewall recommendation.
IANA updates the registry as assignments change. Use Report incorrect data if this snapshot no longer matches the official record, and include the IANA or RFC link so the change can be verified.
Provenance