Database port numbers in the IANA registry
By Liam CooperOctober 27, 2026IANA registry as updated October 26, 2026
In the IANA registry, port 5432 is assigned to postgresql, 3306 to mysql, 1433 to ms-sql-s, 27017 to mongodb and 6379 to redis. Those five are the familiar end of a longer list: 112 registered service names on 109 port numbers carry a database word in their name or label, from questdb2-lnchr in February 2002 to db2c-tls on March 5, 2024.
This article reads that list the way the registry records it: which name sits on which number, on which transport, and since when. It does not say which software listens where in practice: the registry records assignments, not configurations.
The entries behind the familiar numbers
The table picks 22 entries from the match list and its edges: the five names above, the entries whose label names a database product, and companion entries on neighboring numbers. Dates appear only where IANA recorded one; the registry started dating new assignments in the early 2000s, so entries such as mysql and postgresql have none.
| Port | Service | Protocols | Label | Registered |
|---|---|---|---|---|
| 523 | ibm-db2 | TCPUDP | IBM-DB2 | — |
| 1433 | ms-sql-s | TCPUDP | Microsoft-SQL-Server | — |
| 1434 | ms-sql-m | TCPUDP | Microsoft-SQL-Monitor | — |
| 1525 | orasrv | TCPUDP | oracle | — |
| 1527 | tlisrv | TCPUDP | oracle | — |
| 2483 | ttc | TCPUDP | Oracle TTC | — |
| 2484 | ttc-ssl | TCPUDP | Oracle TTC SSL | — |
| 3050 | gds-db | TCPUDP | gds_db | — |
| 3306 | mysql | TCPUDP | MySQL | — |
| 5432 | postgresql | TCPUDP | PostgreSQL Database | — |
| 5433 | pyrrho | TCPUDP | Pyrrho DBMS | Nov 2005 |
| 5984 | couchdb | TCPUDP | CouchDB | Nov 27, 2007 |
| 6379 | redis | TCP | An advanced key-value cache and store | Apr 23, 2015 |
| 7474 | neo4j | TCP | Neo4j Graph Database | Feb 8, 2013 |
| 7687 | bolt | TCP | Bolt database connection | Sep 29, 2016 |
| 8432 | pgbackrest | TCP | PostgreSQL Backup | Jan 26, 2022 |
| 9088 | sqlexec | TCPUDP | IBM Informix SQL Interface | Dec 2005 |
| 9089 | sqlexec-ssl | TCPUDP | IBM Informix SQL Interface - Encrypted | Dec 2005 |
| 11211 | memcache | TCPUDP | Memory cache service | Feb 9, 2009 |
| 26257 | cockroach | TCP | CockroachDB | Sep 29, 2015 |
| 27017 | mongodb | TCP | Mongo database system | Feb 21, 2019 |
| 33060 | mysqlx | TCP | MySQL Database Extended Interface | Aug 6, 2015 |
Two patterns stand out. The older entries are registered on both TCP and UDP: ms-sql-s, mysql and postgresql all hold a UDP number as well. The newer ones do not. redis (April 23, 2015), cockroach (September 29, 2015) and mongodb (February 21, 2019) are assigned on TCP alone, and the UDP number with the same value is held as reserved.
Port 1521 and the Oracle entries
In the registry, port 1521 is assigned to ncube-lm, labelled “nCube License Manager”, an entry last modified on February 14, 2022. The entries whose label names Oracle sit elsewhere: orasrv on 1525, tlisrv on 1527, and ttc and ttc-ssl on 2483 and 2484. Port 1525 is shared: it carries prospero-np as well, a directory service.
The same gap between expectation and registry shows up higher in the range. Port 9200 is registered to wap-wsp, a WAP session service, and 9042 and 28015 have no assignment at all. When a number is not in the registry, the lookup shows it as a free number inside its range rather than guessing.
When database names were registered
Of the 112 database-named services, 62 carry a registration date and 50 do not. The dated ones cluster in the middle of the 2000s, with 10 in 2005 and 6 in 2006, then a slow tail of at most 3 a year after 2012.
The transport pattern changes with the date. Of the 44 dated entries registered before 2011, 8 are TCP-only. Every one of the 18 registered from 2011 on is. That matches the registry-wide shift after RFC 6335, which asked IANA to assign only the transports an application requests.
Encrypted variants
Within the match list, only one pair of plain and TLS names on separate numbers passes this site's counterpart rule: sqlexec on 9088 with sqlexec-ssl on 9089. The Oracle entries form a second pair, ttc on 2483 with ttc-ssl on 2484, which the keyword rule misses because the label “Oracle TTC” names no database term. The counterpart rule is set out on the sources page.
System Ports with a database name
Only 10 of the matches sit below 1024: 65 tacacs-ds, 66 sql*net, 66 sql-net, 118 sqlserv, 150 sql-net, 156 sqlsrv, 446 ddm-rdb, 448 ddm-ssl, 523 ibm-db2 and 888 cddbp. On 66, sql-net replaced the older spelling sql*net, which did not fit the current naming rules; the registry kept both rows.
Where the database numbers sit
The matches are spread thinly across the User Ports. The range with the most is ports 1024–1999, with 20 of them; next come ports 2000–2999 (12), ports 3000–3999 (9) and ports 4000–4999 (9). Unlike x11, which holds the range 6000–6063, no database name is assigned a range of numbers.
Vendor names appear in the labels as written by the applicants: “MySQL” in 7, “IBM” in 4, “Oracle” in 3, “Informix” in 2 and “Microsoft” in 2 of the matched entries. The two postgresql-related entries are the server on 5432 and pgbackrest on 8432, “PostgreSQL Backup”, registered January 26, 2022.
Finding the rest
The match list uses one rule: a service counts when its name contains “sql”, “dbms”, “database” or ends in “db”, or when its label contains “database”, “DBMS”, “SQL”, “DB2”, “key-value” or “DB” as a word. That catches couchdb and pyrrho (“Pyrrho DBMS”) but not memcache on 11211, whose label reads “Memory cache service”. To check any other name, type part of it into the lookup: a search for “sql” returns every name and label that contains it. The range page for ports 5000–5999 lists each entry in context; 5432 sits between park-agent on 5431 and pyrrho on 5433.
Sources. IANA Service Name and Transport Protocol Port Number Registry, updated October 26, 2026 (CC0 1.0). RFC metadata (titles, dates, status) from the RFC Editor rfc-index.xml. Counts computed by knownports.online from the registry file; definitions on the sources page.