Skip to content

URL redirect checker

Trace a public URL’s HTTP redirects. Review each received response, find where the chain ends or stops, and export the complete report.

Check a public URL

Trace its HTTP response redirects, one destination at a time.

One public URL, up to 2,048 characters. Missing scheme defaults to HTTPS; fragments are removed because they are not sent in HTTP requests.

A live check uses your app’s server and makes ordinary requests to the entered website. No AI, paid API or account is required.

What this check covers

Follows 301, 302, 303, 307 and 308 Location responses using GET. Relative destinations are resolved against the current URL. It stops reading each response at the headers.

Only public HTTP/HTTPS destinations on standard ports are supported. Every destination is checked before connecting. Visitor cookies, authorization headers and login credentials are not forwarded.

The checker does not run JavaScript, follow meta refresh, load page assets or reproduce a logged-in browser session. Header timings include DNS and connection work; they are not page-load speed measurements.

Inputs and reports are temporary. Reload or Clear discards them; copying and downloads are explicit exports. Public websites may log the requests made by a live check.

Your redirect report

Observed HTTP responses, with a clear reason when the trace stops.

Enter a public URL to see each received status code, Location header and resolved destination. The report keeps partial responses when a later step fails.

Loops, unsupported destinations, missing or invalid Location values, timeout and redirect limits are reported explicitly. A final 4xx or 5xx response is shown rather than presented as success.

Try an example to inspect a labeled sample without requesting a website.

Direct website requests, without a paid service

The checker uses the app’s own server to inspect HTTP response headers and follow supported Location redirects. It checks public destinations before connecting and limits the number of requests and total time. No AI model or paid data provider is involved.

Server requests can receive different responses from your browser because of cookies, location or bot protection. A final URL is established only when a non-redirect response is received. Read the HTTP redirect status reference.