HTTP Status & Redirect Checker

Check HTTP status and manually follow a public URL’s redirect chain.

The entered public URL is sent to our server for checking. Private network addresses are rejected.

Maximum five redirects. Results reflect this server’s request; other crawlers may receive different responses.

Secure processing Inputs are handled through the configured secure workflow.
Works on all devices Use it on desktop, tablet, or mobile without installing extra software.
No installation Open the page, use the tool, and download or copy your result.

Find out where a public URL sends a request and which HTTP status each hop returns. This checker follows up to five redirects, lists Location values, and reports the final response for the entered HTTP or HTTPS address.

How to Use HTTP Status & Redirect Checker

  1. Enter the exact public URL, including the original hostname and path.
  2. Run the check and read each hop in order.
  3. Confirm the final destination and status, noting any unexpected redirects.
  4. Investigate request-specific errors or verify the final page content before changing rules.

Inspect a redirect before changing it

A redirected URL is not automatically a problem. A deliberate page move can correctly lead an old address to a clean destination. Review the complete chain to identify unnecessary hops, loops, unexpected hosts, or a final error response rather than judging the initial status in isolation.

Example: review an old article URL

Start with the old link that was reported in a crawl or Search Console message. Check whether it reaches the intended article and whether the final response is successful. Then inspect the destination canonical and page metadata separately. A working redirect should not be removed merely to make the old URL return HTTP 200.

Understand request differences

The checker uses a HEAD request first and retries with GET for selected unsupported-method responses. Some sites apply request-specific restrictions, so a blocked or failed request can be inconclusive. Results reflect our server request and do not prove what every browser or search crawler receives.

Use the Redirect Rule Generator for reviewed configuration changes. Use the On-Page SEO Checker for the HTML returned by the final page.

Key Features

  • Bounded public website checks
  • Example inputs
  • Copy and download results
  • No paid API or signup

Common Use Cases

  • Website publishing
  • Content review
  • SEO maintenance

Privacy

The entered public URL is sent to our server for a bounded website check. Page content is processed for this request and is not saved by this tool.

Limitations

Maximum five redirects. Results reflect this server’s request; other crawlers may receive different responses.

Frequently Asked Questions

How many redirects can it follow?
It follows up to five redirects and reports an error when the chain exceeds that bound or loops.
Is a 301 response automatically an SEO error?
No. Review whether the redirect is intentional and reaches the correct final page.
Why can the result differ from my browser?
Sites can respond differently to HEAD requests, user agents, locations, or access restrictions. This result reflects our server request.

Need a tool we do not have?

Tell us what would help and we will consider it for the FreeToolsBundle roadmap.

Request a Tool