Closing port 80?

[hbdragon88]

I recently ran a port scan test on DSLreports.com and everything was filtered or closed except for port 80. DSLReports made a big thing about it - they said that unless you have a web page that you're hosting, don't leave it open. Someone on the message board said that someone could hack your computer through port 80.

Does anyone know how to close it? I don't host a web page.

 

[Moonsinger]

For what system? Linux, Solaris, Win2000, or WinXP?

 

[anarchywrksbest]

You should download a firewall if you don't already have one. I use the basic ZoneAlarm and got this from grc.com's ShieldsUp test:

Your system has achieved a perfect "TruStealth" rating. Not a single packet — solicited or otherwise — was received from your system as a result of our security probing tests. Your system ignored and refused to reply to repeated Pings (ICMP Echo Requests). From the standpoint of the passing probes of any hacker, this machine does not exist on the Internet. Some questionable personal security systems expose their users by attempting to "counter-probe the prober", thus revealing themselves. But your system wisely remained silent in every way. Very nice.

Groovy.

 

[anarchywrksbest]

I suppose you might like to check out:

In depth info on port 80

http://grc.com/port_80.htm

And where to get ZoneAlarm:

http://www.zonelabs.com/store/content/catalog/products/sku_list_za.jsp?lid=pdb_za1

It's the one which seems to have no features but it works.

 

[hbdragon88]

It's for Windows XP, and I have ZoneAlarm Pro. But I don't know how to configure it to close port 80.

 

[funxus]

When you say it's open, I assume it means that you have a program on your computer listening on port 80? If so, what happens when you try to connect to this port yourself? I.e. Run->Telnet->Open localhost 80. Can it connect to it, what happens?

 

[hbdragon88]

Huh.

"Connecting to localhost...Could not open connection to the host, on port 80. No connection could be made because the target machine actively refused it."

 

[funxus]

I guess that means you don't have a program listening to port 80, or that the port is already in use and is connected?

 

[hbdragon88]

What the heck...

I ran a port test on ShieldsUp and it came back as port 80 being closed. I distinctly recall port 80 being open on the DSLReports scan test. Now my problem is port 113 - apparently my computer responded; it said it was closed. Whoops.