check open ports

lsof -Pni4 | grep LISTEN
Tested in Linux and OSX
Sample Output
kopete  1782   user   18u  IPv4  12568      0t0  TCP *:8010 (LISTEN)
sshd    2215   root    3u  IPv4  35583      0t0  TCP *:22 (LISTEN)

By: evenme
2009-08-21 22:51:41

5 Alternatives + Submit Alt

  • While `lsof` will work, why not use the tool designed explicitly for this job? (If not run as root, you will only see the names of PID you own) Show Sample Output

    netstat -plnt
    DopeGhoti · 2011-09-30 19:56:32 0

  • 4
    lsof -Pn | grep LISTEN
    pykler · 2011-09-29 18:21:51 0
  • Check open TCP and UDP ports Show Sample Output

    netstat -plntu
    bolthorn0 · 2011-10-01 12:16:38 0
  • This option selects the listing of all Internet and x.25 (HP-UX) network files. Show Sample Output

    lsof -i
    shsingh · 2011-10-03 02:06:30 0
  • This option is much faster, as it checks only network nodes. Show Sample Output

    lsof -Pi | grep LISTEN
    5partan · 2011-10-03 12:50:18 0

What Others Think

what is wrong with using `netstat`? netstat -an | grep LISTEN does the same and works everywhere, even where `lsof` is not present...
ceesaxp · 579 weeks ago
Someones wont see that unix streams.
bandie91 · 579 weeks ago
netstat -luntp is my choice
Charon · 578 weeks and 5 days ago
netstat don't provide service name and don't work with same behavior in all unix system.
evenme · 574 weeks and 5 days ago
lsof gives all open ports, even those opened by trojans/rootkits which are usually hidden from netstat
zlemini · 549 weeks ago
"won't see unix streams" incorrect; /bin/netstat does indeed show UNIX sockets "netstat doesn't provide service name" which is a good thing, since /etc/services might not be what you expect when diagnosing a stranger's machine. "...usually hidden from netstat" until you encounter malware that has learned to corrupt lsof as well as netstat. My beef is that lsof can hang if there are mounted filesystems that have timed-out (a frequent problem with NFS and CIFS), despite having nothing to do with the TCP/UDP/unix sockets that you are trying to find out about.
Mozai · 468 weeks and 6 days ago
I think it's important to remember that both offer similar information and are useful in diagnosing issues. The more tools in you box the more likely you'll fix the problem. This is especially true if you tend to hop OSes and the command you'd normally use is not available on a different OS. Cheers, Mikel King
mikelking · 452 weeks and 4 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: