Microsoft IIS web servers define extended codes that give a more specific reason of the error:
||Microsoft Knowledge Base articles about server-side troubleshooting
||Execute access forbidden
||Read access forbidden
||Write access forbidden
||See IIS 6.0 operations guide
||SSL 128 required
||IP address rejected
||248043 and 306833
||Client certificate required
||Site access denied
||Forbidden: Too many clients are trying to connect to the Web server
||262635 and 248074
||Forbidden: Web server is configured to deny Execute access
||Forbidden: Password has been changed
||Mapper denied access
||Client certificate revoked
||Directory listing denied
See directory listing forbidden below
||Forbiden: Client access licenses have exceeded limits on the Web server
||Client certificate is untrusted or invalid
||Client certificate has expired or is not yet valid
||Cannot execute requested URL in the current application pool
||Cannot execute CGI applications for the client browser in this application pool
||Forbiden: Passport logon failed
||Forbiden: Source access denied
||Forbiden: Infinite depth is denied
Google servers: Return an error which can be seen on this page:
... but your computer or network may be sending automated queries.
To protect our users, we can't process your request right now.
To continue searching, please type the characters you see below:
Causes and Solutions
- Directory listing: 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.
- You might be able to fix this by appending the name of default web pages (e.g. “index.html”, “index.htm” or “default.html”) after the trailing slash to identify a page within that directory.
- Alternatively, try removing tailing parts of the address (each part being separated by a slash) until you are left with just the domain name of the server (preceded by
- You need to log in: If you cannot access a particular page on a website, then it may be because you need to log in to access that page. Search for a login link on either
This situation is similar to that reported by HTTP 401 Unauthorized errors, except your credentials need to be supplied through cookies that are set from a log in page, rather than through a dialog box that appears when you first attempt to access a page.
- the page that referred to this page that you cannot access, or on
- the default page for the web site (accessed with just the domain name of the web site, and no information after the domain name, i.e. slashes in the address should only appear in the initial
- Your address may be blocked: Servers block access from addresses that have previously made excessive access, e.g. leading to the Google Sorry page. Such blockages usually affect all pages on a web server. While you may not have made excessive access, it is possible that you have been assigned an address (e.g. by your ISP) which someone else previously used excessively.
- Check if your address is blacklisted. Note that servers may maintain independent blacklists, so your address may appear in the server's blacklist, but not public blacklists.
- You may be able to access the site if you try
- through a proxy since your request will then appear to the server to come from the proxy. Of course, the server may also block the proxy.
- again later, by which time your address may have changed.
- The site may be disabled: Some hosting services, e.g. Google sites, may respond with HTTP 403 errors when they have disabled a site (e.g. because it did not comply with their Terms of Service).
Updated 14 June 2012