How to Check Remote Ports are Reachable Using ‘nc’ Command

A port is a logical entity which acts as a endpoint of communication associated with an application or process on an Linux operating system. It is useful to know which ports are open and running services on a target machine before using them.

We can easily list open ports in Linux on a local machine using the netstat or several other Linux commands such NMAP.

In this guide, we will show you how to determine if ports on a remote host are reachable/open using simple netcat (in short nc) command.

netcat (or nc in short) is a powerful and easy-to-use utility that can be employed for just about anything in Linux in relation to TCP, UDP, or UNIX-domain sockets.

# yum install nc                  [On CentOS/RHEL]
# dnf install nc                  [On Fedora 22+]
$ sudo apt-get install netcat     [On Debian/Ubuntu]

We can use it to: open TCP connections, listen on arbitrary TCP and UDP ports, send UDP packets, do port scanning under both IPv4 and IPv6 and beyond.

Using netcat, you can check if a single or multiple or a range of open ports as follows. The command below will help us see if the port 22 is open on the host

$ nc -zv 22

In the command above, the flag:

  1. -z – sets nc to simply scan for listening daemons, without actually sending any data to them.
  2. -v – enables verbose mode.

The next command will check if ports 80, 22 and 21 are open on the remote host (we can use the hostname as well):
nc -zv 80 22 21

It is also possible to specify a range of ports to be scanned:’

$ nc -zv 20-80

For more examples and usage of netcat command, read through our articles as follows.

  1. Transfer Files Between Linux Servers Using netcat Command
  2. Linux Network Configuration and Troubleshooting Commands

That’s all. In this article, we explained how to check if ports on a remote host are reachable/open using simple netcat commands. Make use of the comment section below to write back to us concerning about this tip.

Hey TecMint readers,

Exciting news! Every month, our top blog commenters will have the chance to win fantastic rewards, like free Linux eBooks such as RHCE, RHCSA, LFCS, Learn Linux, and Awk, each worth $20!

Learn more about the contest and stand a chance to win by sharing your thoughts below!

Aaron Kili
Aaron Kili is a Linux and F.O.S.S enthusiast, an upcoming Linux SysAdmin, web developer, and currently a content creator for TecMint who loves working with computers and strongly believes in sharing knowledge.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.


Leave a Reply
  1. This tool sucks, nc -zv says every port succeeds even ones I just make up. Why can’t it ‘just work’ and give real meaningful information as telnet did which wasn’t even designed to test if a port was open.

  2. I hope you are still taking comments…it’s been a while.

    This was almost the best set of instructions I’d run into except it doesn’t cover how to interpret the results. If you provided a sample of success or failure as an example I’d never have to look anywhere else.

    For now, if the results in Redhat 7 are similar to below is the port open or filtered/closed

    Ncat: Version 7.50 ( )
    Ncat: Connected to
    Ncat: 0 bytes sent, 0 bytes received in 5.03 seconds.

    I’m confused by the fact that I’m connected which I think means the port is open but no data was sent or received.


  3. Hi,

    Don’t use this for connectivity checks on Centos 7. This only works on Centos 6. It does not work on Centos 7. You need something like this:

    # echo | nc -w1 $server $port >/dev/null 2>&1 ;echo $?

    Its because redhat/centos distro is changed at Centos 7.

  4. Hi,

    I have Red Hat Enterprise Linux Server release 7.3 (Maipo) installed on my PC.

    When I try either of the below commands, I get the error message as shown:

    # ncat -z 5556
    # nc -z 5556

    Error Message:
    nc: invalid option — ‘z’
    Ncat: Try `–help’ or man(1) ncat for more information, usage options and help. QUITTING.

    ‘–help’ or man() did not provide any details on how to simply scan for listening daemons.

    Any suggestions?

  5. Hello.

    In CentOS 7, there is no package named ‘nc‘.
    Searching for ‘netcat‘:

    $ yum search netcat

    the resulting package is ‘nmap-ncat.x86_64 : Nmap’s Netcat replacement

    If you install this package, the above command will looks like this:

    $ nc --recv-only -z 22

    There is another package ‘netcat-gnu‘. You can read more about this package in:

    Are this observations correct?

    • @Chris

      Yap, correct observations here, package is called ncat instead of nc. However, installation command still works. Many thanks for feedback.


Got Something to Say? Join the Discussion...

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.