Cloudflare Docs
Fundamentals
Visit Cloudflare Fundamentals on GitHub
Set theme to dark (⇧+D)

Network ports

Learn which network ports Cloudflare proxies by default and how to enable Cloudflare’s proxy for additional ports.

Network ports compatible with Cloudflare’s proxy

By default, Cloudflare proxies traffic destined for the HTTP/HTTPS ports listed below.

HTTP ports supported by Cloudflare
  • 80
  • 8080
  • 8880
  • 2052
  • 2082
  • 2086
  • 2095
HTTPS ports supported by Cloudflare
  • 443
  • 2053
  • 2083
  • 2087
  • 2096
  • 8443
Ports supported by Cloudflare, but with caching disabled
  • 2052
  • 2053
  • 2082
  • 2083
  • 2086
  • 2087
  • 2095
  • 2096
  • 8880
  • 8443

How to enable Cloudflare’s proxy for additional ports

If traffic for your domain is destined for a different port than the ones listed above, for example you have an SSH server that listens for incoming connections on port 22, either:

  • Change your subdomain to be gray-clouded, via your Cloudflare DNS app, to bypass the Cloudflare network and connect directly to your origin.
  • Configure a Spectrum application for the hostname running the server. Spectrum supports all ports. Spectrum for all TCP and UDP ports is only available on the Enterprise plan. If you would like to know more about Cloudflare plans, please reach out to your Cloudflare account team.

How to block traffic on additional ports

Block traffic on ports other than 80 and 443 in Cloudflare paid plans by doing one of the following:

Ports 80 and 443 are the only ports compatible with:

Due to the nature of Cloudflare’s Anycast network, ports other than 80 and 443 will be open so that Cloudflare can serve traffic for other customers on these ports. Tools like Netcat will report these non-standard HTTP ports as open.

WAF managed rules or the new Cloudflare Web Application Firewall (WAF) will block traffic at the application layer (layer 7 in the OSI model), preventing HTTP/HTTPS requests over non-standard ports from reaching the origin server.