Open ports

Hello everyone!

I scanned my site (Dolphin 7.0.9.) and found out that 14 ports are opened.

Discovered open port 443/tcp on 174.120.212.00
Discovered open port 8888/tcp on 174.120.212.00
Discovered open port 25/tcp on 174.120.212.00
Discovered open port 993/tcp on 174.120.212.00
Discovered open port 587/tcp on 174.120.212.00
Discovered open port 3306/tcp on 174.120.212.00
Discovered open port 110/tcp on 174.120.212.00
Discovered open port 995/tcp on 174.120.212.00
Discovered open port 143/tcp on 174.120.212.00
Discovered open port 53/tcp on 174.120.212.00
Discovered open port 80/tcp on 174.120.212.00
Discovered open port 22/tcp on 174.120.212.00
Discovered open port 21/tcp on 174.120.212.00
Discovered open port 465/tcp on 174.120.212.00

Does all of these ports need to be opened?

The fact that you're asking this tells me you shouldn't be touching ports on a web server...

Oh, and most of those are ports needed for standard web server applications (FTP, SSH, email, etc.).  You can block those, but keep a keyboard by the server at all times.  Also have a few USB drives handy.

http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml

Some of the ports you listed can be closed, depending on what you are hosting with your server (mail, dns/bind, etc).

I know some ports are essential. But I have concerns about some of them being possible security risk.

All those ports are required for Apache, email, SSH, and FTP.  The only one you may not need is 8888, unless your server has an application making use of it.  Of course, you can always change the default ports, but I see no reason to do this.  As long as you have tough passwords (and don't blindly give out stuff like server access on here...), you ought to be fine. 

 To quote the famous network security consultant and rapper Jay-Z, "You've got 99 problems, but a port ain't one".