WHAT IT DOES
The ports you actually meet, and the ones next to them.
Search by number or by name. Each entry says what listens there, what is usually true when the port is open, and -- where there is one -- the neighbouring port it gets mistaken for: 3306 against 33060, 5432 against PgBouncer on 6432, 587 against 465, 5672 against RabbitMQ's web interface on 15672. A number with nothing registered is explained rather than shrugged at.
Why use it?
Use it to interpret an unfamiliar port in a firewall rule or service configuration and distinguish similar service, management, and encrypted endpoints.
How to use this tool
- Search by exact port number or service words, such as 5432 or PostgreSQL.
- Read the transport and context before applying the result. A service can listen on a non-default port, and this reference does not scan your host.
Details and limitations
- The list is curated rather than imported. IANA registers about six thousand ports and almost none of them are the reason anyone is looking; an entry here has to be a port somebody actually meets in a firewall rule, a compose file, or an error message.
- Searching a number matches that number only. Searching words matches the service name and the description, and every word must match, so two words narrow the list rather than widening it.
- A number with nothing registered still gets an answer: which range it falls in, whether an operating system hands it out to outgoing connections, and what an unexpected listener there is likely to be.
- Ports where exposure is a decision rather than a detail carry a note saying so -- an unauthenticated Redis, a Docker daemon on 2375 that is equivalent to root on the host, RDP on 3389.
- Nothing is scanned or connected to. This is a reference that reads a list in your browser, not a port scanner, and it never sends a packet anywhere.