External port testing
-
-
@black3dynamite said in External port testing:
That one is almost identical to the yougetsignal one. Very simple and straight forward. Do you see any risk in using these tools?
-
GRC ShieldsUp
https://www.grc.com/x/ne.dll?bh0bkyd2 -
@black3dynamite said in External port testing:
GRC ShieldsUp
https://www.grc.com/x/ne.dll?bh0bkyd2Forgot about that one. That's a good one. Thanks
-
@fuznutz04 said in External port testing:
@black3dynamite said in External port testing:
That one is almost identical to the yougetsignal one. Very simple and straight forward. Do you see any risk in using these tools?
Any risks using online tools? Possibly, but your servers is already at risk since its accessible from the Internet anyway.
-
-
@black3dynamite said in External port testing:
@fuznutz04 said in External port testing:
@black3dynamite said in External port testing:
That one is almost identical to the yougetsignal one. Very simple and straight forward. Do you see any risk in using these tools?
Any risks using online tools? Possibly, but your servers is already at risk since its accessible from the Internet anyway.
Yep. Agreed.
-
I like a lot this web:
Test a port using a command
$ telnet portquiz.net 80
Trying ...
Connected to portquiz.net.
Escape character is '^]'.$ nc -v portquiz.net 80
Connection to portquiz.net 80 port [tcp/daytime] succeeded!$ curl portquiz.net:80
Port 80 test successful!
Your IP: 213.97.29.103$ wget -qO- portquiz.net:80
Port 80 test successful!
Your IP: 213.97.29.103For Windows PowerShell users
PS C:> Test-NetConnection -InformationLevel detailed -ComputerName portquiz.net -Port 80
-
You can also use Nmap
https://nmap.org/book/man-port-scanning-basics.html
I use Angry IP Scanner for that but a lot of tools use NMAP
https://angryip.org/ -
nmap is so much lighter and faster than other tools, too.
