2 entries are registered on port 6771. 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.
services registered on this number
2 transports in use
entries encrypted on the wire
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :6771 | Polycom Broadcast | UDP | Network Services | caution | 13.2k |
| :6771 | PolyServe HTTPS | TCPUDPtls | Web Services | safe | 0 |
Port 6771 UDP is typically used by Polycom conferencing systems to facilitate server broadcasts and device auto-discovery within corporate and enterprise networks, enabling seamless deployment and management of voice and video solutions.
port 6771 as Polycom Broadcast →TCP/UDP port 6771 is assigned to PolyServe HTTPS, a vendor-specific service not commonly observed open.
port 6771 as PolyServe HTTPS →The registry says what 6771 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.
ss -ltnp | grep ':6771\b'lsof -nP -iTCP:6771 -sTCP:LISTENnetstat -ano | findstr :6771On 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 6771 — 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