URL redirect checker

URL redirect checker is a free tool that identifies 301 and 302 HTTP redirects for a specific URL and checks a chain of up to 10 redirect steps.

How do HTTP status codes control redirects?

HTTP status codes tell a browser or other client how the server handled a request, and certain 3xx codes instruct the client to request another URL. The server normally includes the new address in a response header named Location.

A 301 response means Moved Permanently. It commonly appears when a site moves to HTTPS, changes domains, or replaces an old page address. Browsers, search engines, and intermediary caches may remember a 301 response, so changes to it can take time to become visible.

A 302 response means Found and usually represents a temporary redirect. Common uses include short-term campaign pages, authentication flows, and routing visitors while a page is unavailable. Other redirect codes exist, including 307 and 308, but this checker specifically identifies 301 and 302 redirects.

How do I read a redirect check result?

Read the status code at each step and determine whether the chain reaches the intended address within the 10-step limit. A response chain can contain one redirect, several redirects, or a repeated sequence that never reaches a useful page.

• Status code is the field where you enter the specific URL to check.

A single 301 from an old URL to its current replacement is usually straightforward. Several redirects may still work, but each additional request adds another point where DNS, TLS, or server configuration can fail. A repeated sequence such as 301, 302, 301, 302 can indicate a loop when the same addresses keep sending the request back and forth.

A redirect chain in practice

Consider a documentation site that has moved to HTTPS and then reorganized one section. If the servers are configured as shown below, the requests would proceed in this order:

1. Input URL is http://docs.example.net/getting-started.
2. The server returns 301 and points to https://docs.example.net/getting-started.
3. That address returns 302 and points to https://docs.example.net/guides/first-steps.
4. The final address returns the page response.

The first step records a permanent HTTP-to-HTTPS move. The second step says the old documentation path is being redirected temporarily. If the path change is intended to be permanent, the site owner may decide that a 301 is more appropriate.

URL syntax can also affect a test. Question marks and number signs act as generic URL delimiters, while ampersands and equal signs are conventions in many query-string formats, so copying only part of an address can change the request. Accented or non-Latin domain names are represented through internationalized domain name processing, while non-ASCII path data is commonly UTF-8 percent-encoded.

Leaving this tool's Status code field empty does not provide a URL to check.

When should I inspect a redirect chain?

Inspect a redirect chain when a URL opens the wrong page, fails after a migration, or behaves differently from the address you configured. The result helps separate redirect configuration from unrelated problems.

• A site migration sends visitors to an old domain. Check the original page URL rather than only the home page. A broad domain rule may work while individual path rules point somewhere else.
• An emailed link opens an error page. Check the complete link, including its query parameters. Marketing and account emails often use an intermediate tracking URL before sending the visitor to the intended page.
• An HTTP address does not reach the HTTPS version. A 301 or 302 can confirm that the HTTP response contained a redirect. It does not prove that the destination certificate is valid or that every browser trusts it.

If the domain does not resolve, no HTTP redirect can be returned because the request has not reached a web server. A Website hosting checker may help identify the hosting provider or infrastructure, but DNS records still need to be examined through an appropriate DNS lookup.

How do DNS and CDN caches affect a redirect test?

DNS caches can return an older address that causes requests to reach an older server configuration, while CDN caches can return an older response even after the redirect rule has been corrected. DNS resolvers retain records according to their time to live, while a CDN may cache a redirect response independently of the origin server.

A browser can also remember a permanent redirect. That explains cases where a fresh server-side check follows the new route but a previously used browser continues to open the old destination. Try a private browsing window or a separate browser profile before changing the server rule again.

DNS does not contain the HTTP redirect itself. It determines which server receives the request. If some resolvers still return an old IP address, different users may reach different servers and receive different status codes until cached DNS entries expire.

Common questions about redirect checks

What happens if a chain has more than 10 redirects?

This checker is limited to 10 redirect steps, so it cannot fully evaluate a longer chain. A chain that reaches that limit should be reviewed for unnecessary hops or a possible loop. Browsers and other clients may also stop following excessively long chains.

Can redirects behave differently for mobile devices?

Yes. A server can choose a destination based on request headers, cookies, location, authentication state, or application logic. Because this check runs on a server, its request context may differ from the context in a particular browser or mobile app.

Should I check a URL that contains a private access token?

Avoid submitting URLs that contain passwords, reset tokens, signed download credentials, or other secrets unless disclosure is acceptable. The input travels to the tool's server over HTTPS and is not stored, but the destination server must still receive the requested URL as part of the check.

Does a URL fragment affect the server redirect?

A fragment is the part after a number sign, such as #billing. Browsers use fragments for client-side navigation and do not send them in the HTTP request, so a web server cannot select a redirect based on that fragment alone. Client-side scripts may still react to it after a page loads.

Can this result confirm that a redirected page is safe?

No. A valid 301 or 302 only shows that the HTTP response contained a redirect. It does not evaluate the destination for malware, phishing, misleading content, or unsafe downloads. Use a Safe URL checker when the destination's reputation or safety is the concern.

Final checks

When tracing redirects, use the exact starting URL that users receive, including the scheme, subdomain, path, and query parameters. Confirm that permanent moves use the intended destination, temporary routes do not become unnecessary chains, and the final host resolves to the current server. If browser behavior still differs, check cached redirects, DNS records, CDN rules, cookies, and certificate configuration separately.