This application will check your network endpoint (18.222.114.31) for open ports.
Note: This will only test TCP ports and will not check if an open port matches the expected service.
You can click on individual entries to test them again.
If you have some of these services exposed on purpose, make sure you secure them properly.
| Port | Protocol | Type | Secure | Result |
|---|---|---|---|---|
| 7 | Echo | Diagnostics | No | Untested |
| 9 | Discard | Diagnostics | No | Untested |
| 13 | Daytime | Diagnostics | No | Untested |
| 17 | QOTD | Diagnostics | No | Untested |
| 19 | Chargen | Diagnostics | No | Untested |
| 21 | FTP | File transfer | No | Untested |
| 22 | SSH | Remote access | Yes | Untested |
| 23 | Telnet | Remote access | No | Untested |
| 25 | SMTP | No | Untested | |
| 37 | Time | Time server | No | Untested |
| 43 | WHOIS | Name resolution | No | Untested |
| 53 | DNS | Name resolution | No | Untested |
| 80 | HTTP | File transfer | No | Untested |
| 88 | Kerberos | Authentication | No | Untested |
| 110 | POP3 | No | Untested | |
| 119 | NNTP | Usenet | No | Untested |
| 137 | NETBIOS name server | Name resolution | No | Untested |
| 139 | NETBIOS session | File transfer | Yes | Untested |
| 143 | IMAP | No | Untested | |
| 179 | BGP | Routing | No | Untested |
| 194 | IRC | Chat (Legacy port) | No | Untested |
| 389 | LDAP | Authentication | No | Untested |
| 443 | HTTPS | File transfer | Yes | Untested |
| 464 | Kerberos | Authentication | No | Untested |
| 513 | RLogin | Authentication | No | Untested |
| 543 | Kerberos | Authentication | No | Untested |
| 544 | Kerberos | Authentication | No | Untested |
| 587 | SMTP | E-Mail (Alternative port) | No | Untested |
| 636 | LDAP | Authentication | Yes | Untested |
| 666 | DOOM | Game | No | Untested |
| 990 | FTP | File transfer | Yes | Untested |
| 992 | Telnet | Remote access | Yes | Untested |
| 993 | IMAP | Yes | Untested | |
| 994 | IRC | Chat (Legacy port) | Yes | Untested |
| 995 | POP3 | Yes | Untested | |
| 1080 | SOCKS | Proxy service | No | Untested |
| 1433 | MS-SQL | Data storage | No | Untested |
| 1512 | WINS | Name resolution | No | Untested |
| 1723 | PPTP | VPN protocol | Yes | Untested |
| 1900 | SSDP | Service Discovery | No | Untested |
| 3000 | HTTP | File transfer (backend) | No | Untested |
| 3001 | HTTPS | File transfer (backend) | Yes | Untested |
| 3306 | MySQL | Data storage | No | Untested |
| 3389 | RDP | Remote access | Yes | Untested |
| 5000 | HTTP | File transfer (backend) | No | Untested |
| 5001 | HTTPS | File transfer (backend) | Yes | Untested |
| 6660 | IRC | Chat | No | Untested |
| 6661 | IRC | Chat | No | Untested |
| 6662 | IRC | Chat | No | Untested |
| 6663 | IRC | Chat | No | Untested |
| 6664 | IRC | Chat | No | Untested |
| 6665 | IRC | Chat | No | Untested |
| 6666 | IRC | Chat | No | Untested |
| 6667 | IRC | Chat | No | Untested |
| 6668 | IRC | Chat | No | Untested |
| 6669 | IRC | Chat | No | Untested |
| 6670 | IRC | Chat | No | Untested |
| 8080 | HTTP | File transfer or proxy service | No | Untested |
| 8443 | HTTPS | File transfer or proxy service | Yes | Untested |
| 9001 | Tor | Proxy service | No | Untested |
| 9030 | Tor | Proxy service | No | Untested |
| 9050 | Tor | Proxy service | No | Untested |
Just because a service is reachable, doesn't means you are not secure.
It's common for routers to listen for DNS and BGP fpr example.
If properly configured by the vendor, these services will not pose a risk.
People will try to break into your system eventually so make sure you only expose services you want to.
For example, do not run an SSH or RDP server if you don't want to remotely access your machine.
The best way to secure services that are not meant for the general public is to not expose them at all.
If this is not an option, setting up a VPN is usually your best bet.
SoftEther is a very well made and easy to use solution.
This way even insecure protocols will stay secure and you don't need to open unnecessary ports in your firewall
or choose ridiculous passwords for the services that you're going to write down into a text file anyways.
You're also not automatically in danger if a vulnerability of a service is discovered because nobody can reach your service
without breaking into the VPN first.
If a VPN isn't an option either, get a static IP for your internet connection and configure the private services on your server to only accept connections from that IP.
In general, you don't want to expose these things unless you are absolutely sure you need to host these services publicly:
Just because a service is not marked as secure doesn't means it can't be secured. It just means that by default, it's not secure and you might need additional steps to secure them. For example HTTP on port 80 can't be secured, but SMTP on port 25 can.