See exactly what a server sends back for any URL. Enter an address and the tool follows every redirect, one hop at a time, and shows the status code, timing and response headers for each step. It also checks the final page for common security headers.
HTTP Header and Redirect Checker
Check the status code, response headers and full redirect chain of any URL, plus a quick security header audit.
Input Section
Result Section
Insights / Tips
- A single 301 from http to https, then a 200, is the ideal chain. More hops slow the page and waste crawl budget.
- Use 301 for permanent moves and 302 only for temporary ones.
- Add missing security headers in your server config or with our .htaccess Generator.
Internal Links
What you will see
- Final status: whether the page ends in 200 OK, a 404, a 500 or another code.
- Redirect chain: every hop, for example http to https, then non-www to www, with the status code of each.
- Response time: how long each step took.
- All headers: server, cache-control, content-type, location and more, for each hop.
- Loop and limit warnings: the tool flags redirect loops and stops after 10 redirects.
- Security header audit: shows whether Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy are present.
How to use the checker
- Enter a URL, with or without https://.
- Click Check Headers.
- Read the summary at the top, then open any hop to see its headers.
- Check the security header list at the bottom and add anything that is missing.
Understanding status codes
- 200 OK: the page loaded normally.
- 301 Moved Permanently: the page has moved for good. Use this for most redirects and for SEO.
- 302 Found / 307 Temporary Redirect: a temporary move.
- 308 Permanent Redirect: a permanent move that keeps the request method.
- 403 Forbidden: the server refuses the request.
- 404 Not Found: the page does not exist.
- 500 / 503: a server error or temporary outage.
Why redirect chains matter
The ideal chain is one 301 from http to the final https address, then a 200. Each extra hop slows the page, wastes crawl budget, and can lose a small amount of link value. Loops make the page unreachable and show browsers an error. If your chain is long, combine the rules in your .htaccess file so each old URL goes straight to the final one.
Frequently asked questions
What is an HTTP header?
It is a piece of information a server sends along with a page, such as its content type, caching rules and security settings.
How do I check a redirect chain?
Enter the starting URL. The tool lists each redirect in order until it reaches the final page.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent and passes ranking signals to the new URL. A 302 is temporary and tells search engines to keep the old URL.
Why does the tool say my security headers are missing?
Your server is not sending them. You can add them in your .htaccess file or your hosting settings.
Can it check pages on my local site or a private network?
No. For safety it only checks public websites.
Is there a limit?
Yes. To prevent abuse, each visitor can run 10 checks per minute.