Port 33002 services

2 entries are registered on port 3300. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.

entries
2

services registered on this number

transport
tcp · udp

2 transports in use

in transit
0/2

entries encrypted on the wire

worst risk
8/10

1 of 2 iana-registered

Services on this port

ranked by lookups
portservicerisk
:3300Debate Gopher DBcaution
:3300Ceph Monitorrisk

01Debate Gopher DBtcp · udp · unofficial · risk 4/10

Port 3300 is commonly linked with backend database communication for a service known as Debate Gopher, likely a specialized or proprietary platform. Supporting both TCP and UDP traffic, this port facilitates data transactions between application services and the underlying database system, performing essential operations like retrieval, storage, and synchronization of debate content. As an unofficial and unencrypted port, it is important to handle it with care to avoid potential security issues.

port 3300 as Debate Gopher DB

Which one is on your host

ask the machine, not the registry

The registry says what 3300 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.

linux
ss -ltnp | grep ':3300\b'
macos
lsof -nP -iTCP:3300 -sTCP:LISTEN
windows
netstat -ano | findstr :3300

On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.

A port number is not a service. Anything may listen on 3300 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.

contribute an entry