Redirect checker
Follow a link hop by hop and see every redirect, its status code and where it finally lands.
- Every hop with its status code
- Final URL and status
- Capped and safe: no private addresses
Give it something to look up — Glee will do the digging.
How the redirect checker works
Redirects decide where visitors and search engines end up. A chain of several hops slows every page load, a temporary 302 where a permanent 301 was meant can split search ranking, and a loop takes the page down. Marketing links, old domains and http-to-https moves are where they usually go wrong.
This checker requests the URL without following redirects automatically, records the status and Location of each response, and repeats until it reaches a final page, a loop or the hop limit. Requests to private or internal addresses are refused.
What each field means
- Chain
- Each hop's status code and next location.
- Final URL
- Where a browser ends up.
Where this check stops
- Redirects are capped and requests to private or internal addresses are blocked.
- Redirects made by JavaScript or meta refresh after the page loads are not followed.
The same check, through the API
Same calculation, same answer, with a key. 5 credits per check ($0.50 per 1,000). A free account includes 1,000 credits a month.
POST /v1/web {"url":"http://acme.com"}
Host: gleanzy.com
Authorization: Bearer $GLEANZY_KEYFrequently asked
301 or 302?
301/308 are permanent and pass ranking to the target; 302/307 are temporary.