Outgoing port tester

This server listens on all TCP ports, allowing you to test any outbound TCP port.

You have reached this page on port 80.

Your network allows you to use this port. (Assuming that your network is not doing advanced traffic filtering.)

Network service: http
Your outgoing IP: 54.80.173.217

Test a port using a command

$ telnet ip-172-31-37-228.eu-west-3.compute.internal 80 
Trying ...
Connected to ip-172-31-37-228.eu-west-3.compute.internal.
Escape character is '^]'.

$ nc -v ip-172-31-37-228.eu-west-3.compute.internal 80 
Connection to ip-172-31-37-228.eu-west-3.compute.internal 80 port [tcp/daytime] succeeded!

$ curl ip-172-31-37-228.eu-west-3.compute.internal:80 
Port 80 test successful!
Your IP: 54.80.173.217
$ wget -qO- ip-172-31-37-228.eu-west-3.compute.internal:80 
Port 80 test successful!
Your IP: 54.80.173.217
# For Windows PowerShell users
PS C:\> Test-NetConnection -InformationLevel detailed -ComputerName portquiz.net -Port 80

Test a port using your browser

In your browser address bar: http://ip-172-31-37-228.eu-west-3.compute.internal:XXXX

Examples:
http://ip-172-31-37-228.eu-west-3.compute.internal:8080
http://ip-172-31-37-228.eu-west-3.compute.internal:8
http://ip-172-31-37-228.eu-west-3.compute.internal:666

I got complains that portquiz is not working on port 445. My hosting company OVH is probably blocking this port. Sorry about that. Feel free to contact them. See my blog post and OVH forum post (french).

Your browser can block network ports normally used for purposes other than Web browsing. In this case you should use the telnet or netcat commands to test the port.

Please also note that this server uses some port for real services (22, 25), so testing with your browser on those ports will not work.

Rate limiting

05/06/2020 : I had to set up Rate limiting on new connections by IP, otherwise the charge was too high for the small portquiz VM. Sorry for that.

Contact/feedback:

Marc MAURICE

See also: