Check your HTTP response headers

While crawling websites Site-Scan and X-Site-Scan collect quite a number of information from the HTTP response headers which the servers send for each request received. However, wrongly configured servers or missing or invalid meta tags can lead to false or missing information in the response headers, and this simple tool shows you the content of your headers as seen by our scanners and other robots.

You can choose to send either a GET or HEAD request for the URL. The content of the headers for a HEAD request depends on your server settings, while the headers for a GET request usually also contain additional information taken from the meta tags of the resource the URL is pointing to. Because this tool shows you the response code for each request submitted, including the response codes resulting from redirects, it can also help you to verify that your server returns the correct error codes, whether your redirects are set up correctly etc.

Simply select whether you want to submit a GET or HEAD request and key in the full URL of the resource in question. Optionally, if you select a value for "If-Modified-Since" this tool will add the respective field to the request header, enabling you to check whether your server replies with a proper "304 - Not Modified" response where applicable.

Fields marked with * are compulsory!

Request:
URL: *
If-Modified-Since:

(By using this tool you agree to our Terms & Conditions)

Notes on usage:

  • This tool requires a browser with meta-refreshs enabled.
  • The requests send by this tool are based on the HTTP/1.1-specifications.
  • This tool accepts redirects based on 301, 302 and 307 response codes.
  • The maximum number of redirects is limited to 7 in order to prevent infinite loops.
  • In case of a redirect, the HTTP response header shown is the one for the final target-URL.
  • When issuing a GET request this tool will display the origin of each HTTP response field, i.e. [S] - Server generated, [D] - Document meta tag, [BOM] - Charset defined in Unicode-signature (Byte Order Mark).
  • In case of a GET request, the maximum amount of data is limited to 10 Kbytes per request in order to reduce the required time and bandwidth. This should be sufficient to parse the head-section of the respective resource, however it might lead to additional messages in the GET response header, e.g. "client-aborted -> max_size".
  • Due to the above limitation the response code might also show "206" instead of "200".
  • In case the request returns the response code 500 (internal server error), this tool will repeat the request for a maximum of 4 times, with a delay of 5 seconds between each request. This is to ensure that the error did not occur because your server was busy or due to routing problems.
  • For an in-depth description of the various header fields and the meaning of their respective values please refer to RFC 2616, available from our download page.
Server powered by
www.ipserverone.com
Scan-technology by M-Press Systems