Enter the full URI path for the page that you are checking server headers for e.g. http://www.seoconsultants.com/tools/headers
There are seven HTTP status codes (200|301|302|304|307|404|410) that we are primarily interested in from an indexing and search engine marketing perspective. It is recommended that you verify your URIs are returning the proper Status-Code in the Server Header.
Our Check Server Headers tool (Single URI Processing with Recursive Results) will identify itself (userAgent) as...
SEO Consultants Directory CSH Bot V2S User IP: 126.96.36.199
Current Date and Time: 2014-07-24T00:27:06-0800
User IP Address: 188.8.131.52
All other server headers are parsed, but they are ignored.
The request has succeeded. The information returned with the response is dependent on the method used in the request.
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.
Test URI: /w3c/status-codes/301
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
Test URI: /w3c/status-codes/302
Admin Note: 2005-03-14 - During the past several months, many discussions have been taking place in the search engine marketing communities concerning what many refer to as pagejacking. What you are about to read concerns everyone who has a website online, this is not an isolated incident. Those who are involved with the page jacking issues may not even know that they are causing harm to those they are linking to using a 302 Found redirect. Many of the 302s are generated from exit tracking scripts.
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
Test URI: /w3c/status-codes/307
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
Test URI: /w3c/status-codes/404
The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval.
If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 Not Found SHOULD be used instead. This response is cacheable unless indicated otherwise.
Test URI: /w3c/status-codes/410
The server encountered an unexpected condition which prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.