PDFConvertCloud logo
PDFConvertCloud

HTTP Headers Checker

Fetch and inspect HTTP response headers for a public URL.

Response headers Status code Redirect location
Fetch response status and headers for a public URL.

How HTTP Headers Checker sends its request

HTTP Headers Checker sends the URL to this site’s backend, validates every resolved address as public, and issues one server-side GET request.

Who receives HTTP Headers Checker data

For HTTP Headers Checker, the target website receives the request from this application server with User-Agent “PDFConvertCloud Network Tools/1.0”; no separate lookup provider is used. HTTP Headers Checker sends the entered public target to this site’s backend for the required lookup or request. Do not place secrets, credentials or private tokens in a HTTP Headers Checker target.

HTTP Headers Checker timeout and redirect behavior

For HTTP Headers Checker, the server timeout is 10 seconds and max_redirects is 0, so redirects are reported rather than followed.

Why HTTP Headers Checker results can differ

For HTTP Headers Checker, headers can vary by requester location, IP reputation, CDN edge, HTTP method, cache, cookies, user agent, authentication, bot controls, and request time.

What you can check

For HTTP Headers Checker, only public HTTP and HTTPS URLs are allowed; localhost, .local, private, and reserved resolved addresses are rejected. For HTTP Headers Checker, only public HTTP or HTTPS targets are accepted; For HTTP Headers Checker, private, reserved, localhost and .local targets are rejected; For HTTP Headers Checker, server request timeout: 10 seconds; redirects followed: 0.

Inputs that may cause a problem

For HTTP Headers Checker, the checker rejects invalid or unresolvable hosts and returns a gateway error when the server cannot fetch the target.

How to understand the HTTP Headers Checker result

For HTTP Headers Checker, the displayed headers are those returned to this backend request and may not match a browser navigation or another network location. To verify HTTP Headers Checker, reproduce its worked example and compare the displayed or downloaded http response headers with the stated expected result. When HTTP Headers Checker returns a file, open the download and inspect every affected page or image.

HTTP Headers Checker example

HTTP Headers Checker sample input: URL = https://example.com. HTTP Headers Checker expected result: The expected result contains the server-observed status code, optional redirect URL, and flattened response-header names and values.

Tools related to HTTP Headers Checker

After using HTTP Headers Checker, you may also find these tools useful: url-status-checker, dns-lookup, ip-lookup.

Continue the workflow

Useful pages connected to HTTP Headers Checker

HTTP Headers Checker is part of the Web & Network Tools section. Use the nearby pages below when the same job needs checking, cleanup, conversion, formatting, or a different output before you finish.

Browse Web & Network Tools

Frequently asked questions

HTTP Headers Checker submits an HTTP or HTTPS URL to the application backend to request a URL and display the response headers returned to the backend. The HTTP Headers Checker page then displays the http response headers.
URL = https://example.com. HTTP Headers Checker expected result: The expected result contains the server-observed status code, optional redirect URL, and flattened response-header names and values.
For HTTP Headers Checker, only public HTTP and HTTPS URLs are allowed; localhost, .local, private, and reserved resolved addresses are rejected.
For HTTP Headers Checker, the checker rejects invalid or unresolvable hosts and returns a gateway error when the server cannot fetch the target.
For HTTP Headers Checker, the displayed headers are those returned to this backend request and may not match a browser navigation or another network location.
HTTP Headers Checker sends the public URL to the application backend, which rejects local or private hosts and makes the HTTP request from the server. HTTP Headers Checker sends the entered public target to this site’s backend for the required lookup or request. Do not place secrets, credentials or private tokens in a HTTP Headers Checker target.