DE

↑ ↓ select, Enter open, Esc close

Follow and show the redirect chain of a URL

harmlessNetworkalle
Adjust the values, the command updates live
user@server
curl -sSIL http://example.com/ | grep -iE '^(HTTP/|location:)'

Follows all redirects with -L and shows the status line and the target from the location header for each hop. This reveals double redirects, for example first to https and then to www, which are better handled in one step. In an endless loop, curl gives up after 50 redirects.

Also searched as

  • check redirect chain curl
  • too many redirects debug
  • http to https www redirect test

Related one-liners

All in Network

Show the number of redirects and the final URL

$curl -sL -o /dev/null -w 'Weiterleitungen: %{num_redirects}\nZiel: %{url_effective}\nStatus: %{http_code}\n' https://example.com/
harmlessSEO checks

Show the redirect chain of a URL with status codes

$curl -sIL "http://example.com/" | grep -iE "^(HTTP/|location:)"
harmlessApache

Test http, https, www and non-www at once

$for u in http://example.com/ http://www.example.com/ https://example.com/ https://www.example.com/; do curl -s -o /dev/null -m 10 -w "%{http_code} $u -> %{redirect_url}\n" "$u"; done
harmlessSEO checks

Check HTTP status codes for a list of URLs

$while read -r u; do printf '%s %s\n' "$(curl -o /dev/null -sS -w '%{http_code}' "$u")" "$u"; done < urls.txt
harmlessNetwork

Check for soft 404s: does a missing page really return 404

$curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' https://example.com/diese-seite-gibt-es-nicht-$RANDOM
harmlessSEO checks

Check maintenance mode for status 503 and Retry-After

$curl -s -o /dev/null -D - https://example.com/ | grep -iE '^(HTTP/|retry-after:)'
harmlessSEO checks

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.