HTTP Header Checker & Redirect Chain
Follow every redirect of a URL hop by hop, inspect all response headers and get a grade for security headers, caching, compression and SEO-friendly redirects.
Results
Final status
Redirects
Total time
Security headers
Redirect chain
Security headers
HTTPS & canonical host
SEO notes
Caching
Compression
Server disclosure
About HTTP headers and redirect chains
Every response a web server sends starts with a status code and a set of headers. Redirects (301, 302, 303, 307 and 308) send the browser on to another URL in the Location header. This tool follows those redirects itself, one hop at a time, so you can see the full chain, how long each hop takes and exactly which headers each server sends.
For search engines, permanent moves should use 301 or 308, and chains should be as short as possible: ideally a single redirect from the old URL straight to the final one. HTTP should redirect to HTTPS, and one of www or the bare domain should redirect to the other so the site has one canonical host.
Security headers such as Strict-Transport-Security, Content-Security-Policy and X-Content-Type-Options tell browsers to enforce HTTPS, limit which scripts may run and block content-type sniffing. Use the CSP Header Builder or the Web Server Config Generator to add the ones you are missing.
Was this tool useful?
Thanks for your feedback!
Could not send your feedback. Please try again later.
Frequently Asked Questions
It requests the URL you enter, follows every redirect one hop at a time (up to 10) and shows each hop's status code, response time, Location and all response headers. The final response is graded for security headers, caching, compression and SEO-relevant redirects.
Use 301 (or 308) when a page has moved for good, such as HTTP to HTTPS or an old URL to a new one: search engines then index the new URL and pass ranking signals to it. Use 302 or 307 only for genuinely temporary moves.
Seven headers earn points out of 100: HSTS (25), Content-Security-Policy (25), X-Frame-Options or CSP frame-ancestors (15), X-Content-Type-Options (10), Referrer-Policy (10), Permissions-Policy (10) and Cross-Origin-Opener-Policy (5). A+ needs at least 95 points with HSTS and a CSP without unsafe-inline scripts.
Some sites send different redirects or headers to search engine crawlers or phones. Switching the user agent shows what each of them gets. Sites that verify Googlebot by IP address may treat our request as a normal visitor.
GET asks for the full page (we read only the first 32 KB and discard it); HEAD asks for the headers only. Most servers answer both the same way, but some return different headers or do not support HEAD, so GET is the default.
No. Every hop, including each redirect target, must resolve to a public IP address. Redirects to private, loopback or cloud metadata addresses are blocked and shown as blocked in the chain.
Related Tools
All SEO Tools →Hreflang Tag Generator & Checker
Generate hreflang tags, HTTP Link headers and XML sitemap en...
Free SEO Analyzer & Website Audit Tool
Comprehensive SEO analysis for any website. Check technical...
Free XML Sitemap Generator
Generate XML sitemaps for your website and submit to Google...
Hash Generator
Generate MD5, SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512 h...
HMAC Generator & Webhook Signature Verifier
Generate HMAC-SHA256, SHA-1 and SHA-512 signatures and verif...
Bcrypt Hash Generator & Checker
Hash passwords with bcrypt using a configurable cost factor...