Skip to main content

List of Blocked Ports

Proxyrack avatar
Written by Proxyrack
Updated today

To ensure optimal performance, network stability, and security across our proxy infrastructure, we block access to specific ports commonly associated with abuse, spam, malware, or services that are not supported via our proxies.

If you're experiencing connectivity issues or your tool is failing to connect, it's worth checking whether the port you're trying to access is on the blocked list.

Below is the complete list of ports we currently block across our network.

Blocked Ports

389, 379, 390, 3268, 636, 691, 102, 135, 522, 24, 25, 2525, 25025, 2526, 2527, 2528, 5252, 110, 143, 587, 995, 993, 55555, 52943, 43594, 4080, 3000, 3478, 4080, 8008, 8080, 8090, 10001, 2082, 2083, 2086, 2087, 2089, 465

Why Are These Ports Blocked?

Most of these ports are associated with:

  • Email protocols (SMTP, IMAP, POP3)

  • Remote desktop and shell access (SSH, RDP, Telnet)

  • Database connections (MySQL, MSSQL, PostgreSQL, etc.)

  • P2P, proxy chaining, and tunneling

  • Malware and botnet behavior

  • DDoS amplification vectors

  • Ports with high abuse reports or scanning activity

By blocking these ports, we reduce the risk of abuse and maintain the integrity of our services for legitimate users.

Need to Access a Specific Port?

If you believe a specific port should not be blocked for your use case, please contact our support team. While we don't typically make exceptions, we're happy to review requests on a case-by-case basis.

For any questions or help, feel free to contact support or visit our Help Center.

Did this answer your question?