Check URL redirect chains and HTTP status codes
Enter a starting address to see where server HTTP redirects lead. The tool displays the URLs and statuses of observed steps within its time and redirect-count limits.
Enter the starting public HTTP or HTTPS address.
The tool follows HTTP 301, 302, 303, 307 and 308 redirect responses.
A successful check shows the observed addresses and their HTTP statuses.
Chain length, time and response size are limited; results may be cached for five minutes.
JavaScript and meta-refresh navigation are not executed as in a browser.
Changes require separate edits to the website redirect rules.
Enter a public URL without query parameters, a fragment or login credentials.
Only public HTTP/HTTPS addresses are checked, with time, size and redirect limits. Results are observations, not guarantees.
Compare each step with the intended address
After a migration or URL change, it helps to see where an old link leads. Extra steps may come from separate server and CDN rules. Compare the result with the intended final address and investigate the purpose of each transition.
Useful inspection scenarios
- Moving an HTTP address to HTTPS
- Addresses with and without www
- The new address of a renamed page
- URL variants with and without a trailing slash
Frequently asked questions
Why might a browser navigate somewhere else?
A browser may also use JavaScript, meta-refresh and its own cache. This tool follows server HTTP redirects. Compare the same starting address with the browser network log when investigating a difference.
What would you like to make?
A short description and a way to reach you are enough to start.
info@siteman.az ↗+994 70 270 58 00