Follow URL Redirect Checker

path) > 0) { $steps = count($request->path) - 1; $count = ($steps == 1) ? '1 redirect' : $steps.' redirects'; echo "

Final destination

The URL you traced had ".$count." and ended here:

getFinalRedirect()."\" target=\"blank\"> ".$request->getFinalRedirect()."

Redirect trace

"; foreach ($request->path as $step) { $item = $step['step']; $url = $step['url']; $code = $step['code']; $next = ($step['next']) ? 'Yes' : '--'; echo " "; } echo "

User agent: ".$request::USER_AGENT."
Step	Request	Code	Redirect
".$item."	".$url."	`".$code."`	".$next."

"; } else { echo "

Trace a URL's redirects

Enter a URL in the search box above to derive the final resolved URL after all redirects. The script runs recursive cURL requests until we get a 200 status code. This is helpful to get around link tracking or original URLs that Pi-hole outright blocks (like email links).

I used to use wheregoes.com which is a good, reliable service, but decided to roll my own for privacy reasons. Absolutely nothing is logged as all URL searches are via POST and that's not currently included in my nginx logs.

Technical details

User agent

Other cURL settings

"; } ?>

HTTP response status codes

Informational (1XX–199)

100 Continue: Continue the request or ignore the response if the request is already finished.
101 Switching Protocols: Sent in response to a client's Upgrade request header and indicates the protocol the server is switching to.
102 Processing: Server has received and is processing the request, but no response is available yet.
103 Early Hints: Intended alongside Link header to let the user agent preconnect or start preloading resources while the server prepares a response.

Successful (2XX–299)

200 OK: The request succeeded.
201 Created: The request succeeded, and a new resource was created as a result.
202 Accepted: The request has been received but not yet acted upon.
203 Non-Authoritative Information: Typically for mirrors of original resources, the returned metadata is not exactly the same as is available from the origin server but is collected from a local or a third-party copy.
204 No Content: There is no content to send for this request, but the headers may be useful.
205 Reset Content: Tells the user agent to reset the document which sent this request.
206 Partial Content: Only part of a resource is sent in response to the Range header.
207 Multi-Status: Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
208 Already Reported (WebDAV): Used inside a <dav:propstat> response element to limit repetition.
226 IM Used: For HTTP Delta encoding when the server has fullfilled a GET request and the response is from 1+ instance manipulations.

Redirects (3XX–399)

300

Client error (4XX–499)

100

Server error (5XX–599)

500

See RFC 9110 for official documentation on each status code.