Skip to content
ToolMug

HTTP Header and Redirect Checker

Enter a URL to follow its redirects hop by hop and see each status code, response headers and timing, plus where it finally lands — for debugging HTTP-to-HTTPS and www redirects, loops, caching and security headers, or expanding short links.

Processed on our server; nothing is stored

How to use

  1. Enter a URL (https is assumed if you leave out the scheme).
  2. Click Look up to see each hop’s status code and redirect target in order.
  3. Open Response headers to see everything the server sent.

Options explained

Redirect chain
Up to 10 redirects are followed; loops or redirects to non-HTTP addresses stop the check with a note.
Response headers
Including Cache-Control, Content-Type, Strict-Transport-Security and Content-Security-Policy, sorted by name.
Restrictions
Only public addresses on ports 80, 443, 8080 and 8443 can be checked; private addresses are blocked.

How the check is made, and headers worth reading

Each hop is requested with a GET, not a HEAD, so you see what a browser would receive. The tool reads only the start of the body, up to 64 KB, and ignores it, so large files are not downloaded. A relative Location header is resolved against the current address, and a redirect that points to a scheme other than http or https stops the check. The time for each hop and the server address are shown next to its status.

These response headers are the ones most often checked:

Header What it controls
Location The address a 3xx response redirects to
Cache-Control How long browsers and caches may reuse the response (RFC 9111)
Content-Type The media type and character set of the body
Strict-Transport-Security Tells browsers to use only HTTPS for the site for a period (RFC 6797)
Content-Security-Policy Which sources scripts, styles and images may load from
X-Content-Type-Options nosniff stops browsers from guessing a different content type
Referrer-Policy How much of the page address is sent to other sites
X-Frame-Options Whether the page may be shown in a frame (RFC 7034)

Frequently asked questions

What is the difference between 301 and 302?

301 is permanent — browsers and search engines remember the new address; 302 is temporary. Use 301 for domain moves and HTTP-to-HTTPS.

Why is there a 200 after the redirects?

A final 200 means the real page was reached. Ending in 4xx or 5xx means the target is missing or the server failed.

Can I check sites with certificate problems?

Yes; certificates are not verified here. Use the SSL checker for those.

Privacy

This tool needs our server: what you enter or upload is sent over HTTPS, processed and then discarded, never stored. Server access logs record IP addresses and request URLs, used only to prevent abuse.

Related tools