Port 3020Common Internet File System (CIFS)

IANA assigns TCP/UDP 3020 to CIFS, but SMB/CIFS file sharing is normally found on TCP 445 or legacy TCP 139.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 993 of 4,426 · top 22%

also known as cifs, SMB

Technical Details

what runs on :3020

The IANA entry associates CIFS with TCP and UDP 3020, but there is no standard CIFS handshake or framing used on this port in common deployments. SMB/CIFS normally uses TCP 445 for direct hosting; older NetBIOS-hosted SMB uses TCP 139, with NetBIOS name and datagram services on UDP 137/138. On those TCP ports, clients negotiate an SMB dialect and then exchange framed file, printer, and session operations; 3020 should not be assumed to provide that service merely because of its registry assignment.

Security Information

exposure of :3020

risk score

2/ 10safe

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

file transfer averages 3.5 across 168 ports — this one sits 1.5 below.

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

A real SMB/CIFS listener can expose file shares and authentication to password guessing, credential-relay attacks, and vulnerabilities in outdated implementations; it should not be exposed directly to the internet. SMB encryption is not guaranteed by default, and the low practical exposure of 3020 reflects that it is not a commonly deployed SMB port, not that an SMB service there would be safe.

the 8 most looked-up other ports in file transfer — 168 ports carry that label.

risk mix of the 8 listed

  • caution100%

1 of 8 encrypted