The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. It is accessing a URL for which you don't have permission.

The Web server (running the Web site) thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the resource identified by the URL is forbidden for some reason. The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.

If the address that you tried to access only contains a domain name (e.g. www.example.com) or ends with a slash (/) then you will receive a HTTP 403 error when the server is configured not to allow directory "folder" listings. Such configuration is common because it allows the site to force you to navigate through it using links in approved web pages, and also allows it to hide files in those directories that may only exist for internal use. If you are monitor your website through 100pulse, we will intimate whenever you encounter 403 status code error through e-mail or Short message service.