Port 2779LBC Sync

IANA assigns TCP and UDP port 2779 to LBC Sync; no operator or public deployment is documented.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
1/10

safe

lookups
0

rank 993 of 4,268 · top 23%

Technical Details

what runs on :2779

LBC Sync is registered on port :2779 over tcp and udp. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :2779

this machine
# linux
sudo ss -tulpn 'sport = :2779'

# macos / bsd
sudo lsof -nP -i :2779

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :2779
another host
nmap -sV -p T:2779 <host>
sudo nmap -sU -sV -p U:2779 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :2779

risk score

1/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

no security notes recorded for :2779 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

ports registered around :2779, by lookups.

portservicerisk
:2809IBM WebSphere WAS Bootstrap RMIcaution
:2809CORBA IIOP URLcaution
:2735NetIQ Monitor Consolecaution
:2784WWW developmentsafe
:2718PN Requester 2safe
:2726TAMSsafe
:2720wkarssafe
:2734CCS Softwaresafe

risk mix of the 8 listed

  • safe63%
  • caution38%

0 of 8 encrypted