FREE TOOL
Free redirects tester
Paste a URL and see its full redirect chain - every hop, status code, final destination, and the platform each rule lives on.
Different result in your own browser? It's likely caching an old 301. Open the URL in incognito or hard-refresh. Learn more.
The big picture
A working redirect and a correct one aren't the same thing
Open a link in a browser and you see one thing: the page that loads. You don't see how it got there - the extra hop, the 302 that should be a 301, the bounce through http, the query string dropped on the way. The useful question isn't "does the link work?" It's "where does it actually land, and how clean is the path?"
A redirect that loads a page looks fine to everyone who isn't inspecting it. But a 302 in place of a 301 tells search engines the move is temporary, so the old URL keeps the ranking. Four hops instead of one add latency and strip referrer data. A stale rule quietly points /pricing at the homepage. Nothing throws an error - it just leaks rankings, traffic, and attribution a bit at a time.
Then there's finding where the redirect is set at all - a Cloudflare rule, an .htaccess nobody has opened in years, a CMS field, a DNS forward, app middleware. Half the fix is knowing which system to log into. This tester follows the whole chain and names the platform behind each hop, so you start with an answer instead of a hunt.
Checking one URL is a paste-and-read job - that's this page, free, no account. Checking every URL across a domain move, on a deadline, with more than one team involved, is a different job. That's Redirect Supply: one place to map, verify, and launch every redirect in a migration.
FAQs
Everything you might ask about testing a redirect
Is it free? Do I need an account?
Free, and no - paste a URL, hit Test. Nothing to sign up for.
What does "Both" test?
It runs the chain twice - once from http://, once from https:// - so you can see how each entry point behaves.
How many redirects will it follow?
Up to 15 hops, plus one HTML meta-refresh. Client-side JavaScript redirects are flagged but not followed.
My browser follows this redirect differently. Why?
Almost always a cached 301 - browsers store permanent redirects hard. Open the URL in a private window to see the current behavior.
How do you know where each redirect is configured?
It fingerprints the response headers - server, cf-ray, x-redirect-by, and others - and matches known platforms like Cloudflare, Vercel, or Framer. "Medium" or "low" means a strong guess, not a certainty; the raw signals are under Details.
Can I check every redirect for a whole site move?
This page is one URL at a time. A full domain migration - many URLs, a launch date, more than one team - is what Redirect Supply is built for.
Can I share a result?
Yes - the URL and scheme go into the address bar, so a copied link opens the same result for someone else.
Does it work on internal or localhost URLs?
No - only public URLs. Anything resolving to a private, loopback, or internal address is rejected.
Have more questions?