Free tool · 🧾 HTTP headers & redirect checker
Every hop, every header,in one request.
Debug redirect loops, www/HTTPS canonical chains, missing security headers, cache problems and slow TTFB — the view we open first on any “site is weird” ticket.
Up to 8 redirect hops are followed. Only public hosts. Nothing is stored.
What it checks
Everything we would look at first on a client call.
Free, no sign-up, no email gate. If the report shows red, the fix is written next to it — and we are one click away if you would rather we did it.
- Redirect chain with status, location and time per hop
- Final headers, server, CDN, compression and content-type
- Security headers scorecard with fixes
- Cache-control, ETag, Last-Modified, Age
- TimingDNS, connect, TLS, TTFB, total
FAQ
Common questions
How many redirects are OK?
One (http→https or www) is normal; two is tolerable; more wastes crawl budget and ~100–300 ms per hop. Make http://example.com jump straight to the final https://www URL.
Which security headers matter most?
HSTS and X-Content-Type-Options are free wins; a CSP takes work but blocks most injected-script attacks; X-Frame-Options/frame-ancestors stops clickjacking.
My TTFB is 1.5 s — why?
Usually uncached PHP/WordPress, a slow database query or a far-away server. Enable page caching, use a CDN, or move hosting closer to your users.