How to Check a URL Redirect Chain (Free Online Tool)

August 26, 2026 · 4 min read

When you type a URL into a browser, you often don't land on the address you typed. The server may send your browser through two, three, or more hops before it reaches the final page. Each hop is an HTTP redirect — and when one of them is wrong, you get slow loads, lost SEO value, or a broken page.

This guide shows how to trace a redirect chain in seconds with our free URL Inspector, and what to do about the problems it finds.

Check a redirect chain now: paste any URL into the free URL Inspector. You'll see every hop, every status code, all response headers, and the SSL certificate of the final destination — no signup.

What a redirect chain looks like

A typical chain after migrating to HTTPS might be:

http://example.com → 301 → https://example.com
https://example.com → 301 → https://www.example.com/
https://www.example.com/ → 200 OK

Each hop costs an extra round trip. Google follows up to 10 hops, but every unnecessary hop dilutes link signals and adds latency — especially on mobile connections.

The status codes that matter

Code	Meaning	Use for
301	Permanent redirect	Domain migrations, HTTPS upgrades, renamed pages. Passes full SEO value.
302 / 307	Temporary redirect	Short-term changes: maintenance pages, A/B tests. Search engines keep the old URL indexed.
308	Permanent, method-preserving	Like 301 but guarantees POST stays POST. Used by CDNs like Cloudflare Pages.
Meta refresh / JS	Client-side redirect	Avoid. Slower and unreliable for search engines.

The most common mistake is using 302 where 301 was intended. If a page has moved permanently but you redirect with 302, Google may keep showing the old URL — or worse, treat the redirect as soft-deleted content.

Common redirect problems (and fixes)

Chains longer than 3 hops. Point the first redirect directly at the final URL instead of at another redirect.
Redirect loops — the browser gives up with ERR_TOO_MANY_REDIRECTS. Usually caused by conflicting rules (e.g. www and HTTPS enforced by two systems that each undo the other).
HTTP → intermediate → final. Redirect http directly to the final https URL in one hop.
Redirects on internal links. Update links inside your own site to point at final URLs — crawlers shouldn't have to follow redirects between your own pages.
Mixed 200-content behind a redirect that serves a homepage instead of the requested page (soft 404s). Check the final URL matches what you asked for.

Don't forget the SSL certificate at the end of the chain

A redirect can mask an SSL problem: the first hop works, but the final host has an expired certificate, a chain that isn't trusted, or TLS 1.0 only. Visitors see the error at the last second — after waiting through every hop.

The URL Inspector checks this automatically: for every URL you inspect, it performs a live TLS handshake against the final host and reports the issuer, expiry date with days remaining, TLS version, whether the chain is trusted, and pass/fail checks for hostname match, key strength, and self-signed certificates. Certificates under 30 days are flagged as warnings; expired ones fail outright.

Security headers worth checking while you're there

The same inspection shows the HTTP security headers of the final response. The big ones:

Strict-Transport-Security (HSTS) — tells browsers to always use HTTPS.
Content-Security-Policy — mitigates XSS and injected scripts.
X-Content-Type-Options: nosniff — stops MIME-type sniffing.
X-Frame-Options / frame-ancestors — prevents clickjacking via framing.
Referrer-Policy — controls how much referrer data leaks to other sites.

For a full walkthrough of every header, see the HTTP headers reference.

Try it

Paste any URL into the free URL Inspector — you'll get the complete redirect chain, all response headers, security header analysis, and a live SSL/TLS report in one view. Nothing is stored, no account needed.

If you also monitor uptime for your sites, take a look at DeskUptime — a lightweight desktop uptime monitor for macOS, Linux, and Windows.