When I go to my site nypd.cc I get a 403 Forbidden page. Do you see the site or the 403 page when you try to access the URL (I'm trying to see if it is really just my IP or if all bots are banned -- hopefully not Google)? How can I fix this problem?
I see Is the site new? Have you given enought time for the DNS to propagate? Have you tried clearing your browser cache?
Yeah, I tried two different browsers and the DNS was last changed about a week ago. But I was able to access it about three hours before I posted my question so I am not sure what's going on.
It's probably just an issue with one of the main "ROOT" DNS servers or even the way it is routing to your host providers DNS. I would say everything should be resolved within 48 hours. If not, I recommend contacting your Hosting or Domain name provider.
Nothing to do with DNS most likely. Change the "permissions" on your folder and files. To test it, you can try chmod'ing to 777. But change it to something more secure later.
First, thanks for the help! Secondly, I think I may know where the problem lies. The domain is hosted on a parking service's DNS. I tried to change the ad code using the companies old template system and apparently now that they have a new template system for their customers they no longer support the old system. For some reason, any attempt to modify the settings (adding or subtracting HTML) in my account triggers the IP ban bot. This has occured to other people's sites on this system. My question now is why would adding or subtracting (modifying) HTML on a web site trip a "Bot Trap"? It seems as though the ban only occurs on the IP address where the changes have been attempted. I can access my site through proxies.
Oh, so you use a free web site generator thing? Sounds like you have an over paranoid host. I would contact them, let them know of the issue, and have them un-ban your ip. You can also try changing yor IP by unplugging your modem and router.
Contacted the administrator. They probably had something screwy on their server. Other domain name owners had the same issue. Now everything is fine. Thanks for your advice DP'ers!