...

Blocked Ports and IPs

Published on

All data is current as of

For security reasons, some network ports and IP addresses are blocked. These measures help prevent unauthorized access, protect services from attacks, and reduce the risk of malicious traffic spreading. Below is a list of blocked ports and their purpose.

Blocked Ports

PortProtocolDirectionDescription
137TCP/UDPIngressNetBIOS Name Service (NBNS), used for naming in Windows networks.
138UDPIngressNetBIOS Datagram Service (NBDS), datagram transmission.
139TCPIngressNetBIOS Session Service (NBSS), provides session connections.
445TCPIngressSMB (Server Message Block) over TCP/IP, file and printer sharing.
1688TCPIngressMicrosoft Key Management Service (KMS), product activation.
25TCPEgressSMTP, email sending (unblocked on request).
23TCPIngressTelnet, outdated insecure remote access protocol.
1900UDPIngressSimple Service Discovery Protocol (SSDP), part of UPnP.
3702TCP/UDPIngressWeb Services Dynamic Discovery (WS-Discovery), web services discovery.
11211UDPIngressMemcached, distributed data caching.
17TCP/UDPIngressQuote of the Day (QOTD), outdated string message protocol.
19TCP/UDPIngressCharacter Generator Protocol (CHARGEN), outdated service often used by attackers in DDoS.
53413UDPIngressRemote Code Execution (RCE) vulnerability on Netcore/Netis routers via UDP port 53413 (backdoor).


We also block so-called bogons — IP addresses from private or reserved ranges (including ranges defined in RFC 1918) that should not be used on the internet. This helps prevent internal addresses from leaking into public Internet traffic and protects against IP spoofing attacks.

Blocked RFC 1918 address ranges:

  • 10.0.0.0/8: from 10.0.0.0 to 10.255.255.255;
  • 172.16.0.0/12: from 172.16.0.0 to 172.31.255.255; 
  • 192.168.0.0/16: from 192.168.0.0 to 192.168.255.255.