Which ports does your server answer on?
Enter the domain or IP of a public server your company runs. We try a fixed set of common TCP ports and list the ones that accept a connection. Addresses on private or local networks won’t be scanned.
What an open port means for your business
Agencies and in-house teams run this check after a site launch, a hosting move or a new proxy setup, to confirm a server answers on the services it should and nothing else. The table groups the ports we test.
| Group | Services in the scan | If it shows as Open |
|---|---|---|
| Web | HTTP, HTTPS and their usual alternates | Expected on any server that hosts a website or online shop. |
| SMTP and submission, POP3 and IMAP, plus their secure versions | Normal on a mail server. On a web server, ask whoever manages it why they are open. | |
| Remote access | SSH, remote desktop and VNC | Admin entry points. Many companies allow them only from known office addresses. |
| Databases | MongoDB, MySQL, PostgreSQL and Redis | Rarely meant to face the internet. Raise an open one with your developer or host. |
| Proxy and DNS | SOCKS, the Squid proxy default and DNS | Expected on proxy gateways and name servers, not on a typical website. |
| File transfer | FTP | An older service; many hosts now offer SFTP over SSH instead. |
Closed means no connection was made within the time limit, whether the port was shut, filtered or slow to reply. The test runs from our network, so a port your firewall opens only to office addresses will show as Closed here. Testing a proxy on a port outside this list? Run it through Ping, which accepts any port.
Only scan servers your company owns or has written permission to test. Scanning anyone else’s systems may run against their policies as well as local law.
