Well, that rule will reject ALL PACKETS that are directed to that chain (given the name of the chain, it might be fed from your INPUT chain).

Are there any rules in that list that have "-j RH-Firewall-1-INPUT" in them?

This is not the ONLY culprit, but once you fix the firewalling in your ISP's edge router, this may be the next one you hit.

Sincerely
Bill Jennings

Well then, I better list out what I have in my iptables

# Firewall configuration written by redhat-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -i eth0 -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT

hello.. I am back.

Well, I think you guys gonna kill me.

The reason why the public couldn't get in is because they have assigned a private IP to me! Urghh!! I should have already suspected that. Now they have re-assigned me a public IP. The website is now viewable.

You guys were really nice. Thanks for all your precious times.

Luv u all