Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

enter image description here

I just did a port check with CPorts and I find that google chrome has so many local ports open in the range of 7713 - 7794. They are all connects to 80 or 443 on the other end.

Why does google chrome need all these ports?

share|improve this question
Those aren't local ports that are open. Those are connections that are established. – David Schwartz Apr 7 '12 at 5:04
@DavidSchwartz, Semantics.... there's no server on his machine listening at those ports, but they are apparently open since they can receive traffic from the host server. – Pacerier May 21 '15 at 6:31
up vote 5 down vote accepted

They are the local port numbers of the sockets connected to the servers that host the websites you're browsing right now.

In TCP/UDP socket communication, there is always a port associated with a socket. For both the receiving and the sending side.

HTTP most commonly uses port 80. 443 is most commonly used by HTTPS.

The local port numbers have no real relevance or meaning. It's nothing to worry about.

share|improve this answer
Since Chrome 26 the build-in asynchronous DNS is enabled per default. This requires several dozen of additional UDP ports to be open. However, I have not found any documentation as to why in the world asynchronous DNS needs that many open ports. Do you have a clue? – king_julien Apr 8 '13 at 9:27
@gentmatt: I'm not aware that it requires any additional open ports. Unless you're referring to outbound connections. Either way, you might want to ask a new question about it. – Oliver Salzburg Apr 8 '13 at 10:48
There is already a very similar question to my problem at… It's not so distict that I would require a new question. (Instead, I edited the answer in an attempt to bump the question to receive more attention.) I'm very confident that the open ports are linked to Google Chrome as I use a custom firewall to monitor network connections. The firewall reported all the requests to open additional ports after the latest Chrome 26 update. – king_julien Apr 8 '13 at 10:57
If I disable asynchronous dns, remove the new port rules, and then restart Chrome, the firewall no longer requests to open all these additional ports. – king_julien Apr 8 '13 at 10:59
@gentmatt: I also just updated, my firewall is not showing any additional open listening ports, neither does netstat. Maybe there's more to it. I would appreciate if you joined us in Root Access. Maybe we can analyze this better in chat :) – Oliver Salzburg Apr 8 '13 at 11:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .