Redirect Checker: Follow a URL's Redirect Chain
Follow a URL's redirects and unshorten short links.
Use via API
Follow a public URL's redirect chain hop by hop (up to 10 hops), returning each status, Location and headers, the final URL, and whether it loops. Send JSON, get JSON back; this one reaches the network from PithLab’s server.
POST https://pithlab.com/api/v1/tools/redirect-checker
curl https://pithlab.com/api/v1/tools/redirect-checker \
-H "Authorization: Bearer $PITHLAB_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"http://example.com"}'About the Redirect Checker
Follow every redirect from a URL to its final page. See each hop's status code and target, unshorten short links, and spot loops, long chains and HTTPS downgrades.
How to use the Redirect Checker
- Paste a URL or a short link, such as a bit.ly link from an email.
- Press Follow. PithLab's server requests each URL in turn without loading the pages.
- Read each hop's status code and where it points, and the final URL at the bottom.
- Check the warnings for loops, long chains and temporary redirects that should be permanent.
Examples
Input
http://example.com
Output
Final URL https://example.com/ if the site redirects to HTTPS
Frequently asked questions
Is it safe to check a suspicious short link here?
Yes. PithLab's server requests the links, not your browser, and it never downloads or runs the pages. You see where the link leads before deciding whether to open it.
What's the difference between 301 and 302?
301 means the page has moved permanently, so search engines move rankings to the new URL. 302 is temporary, so they keep the old one. 308 and 307 are the same pair, but guarantee the request method isn't changed.
Why doesn't it follow JavaScript or meta refresh redirects?
Those happen inside a page after it loads. This checker reads HTTP redirects only, which is what search engines and most link previews follow first.