DE

↑ ↓ select, Enter open, Esc close

Check HTTP status codes for a list of URLs

harmlessNetworkalle
Adjust the values, the command updates live
user@server
while read -r u; do printf '%s %s\n' "$(curl -o /dev/null -sS -w '%{http_code}' "$u")" "$u"; done < urls.txt

Reads the file line by line and fetches each URL with curl. It prints the status code and URL, so the list can be filtered further with sort or grep -v '^200'. Useful after a relaunch for checking old URLs for correct redirects and missing pages.

Note: Redirects are not followed, so a 301 is the desired result for old URLs. With -L in the curl call, the status of the target page appears instead.

Also searched as

  • check status codes of multiple urls
  • bulk check redirects after relaunch
  • find 404 pages from url list

Related one-liners

All in Network

Show the redirect chain of a URL with status codes

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

Follow and show the redirect chain of a URL

$curl -sSIL http://example.com/ | grep -iE '^(HTTP/|location:)'
harmlessNetwork

Show the HTTP response headers of a website

$curl -sSI https://example.com/
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

Check the status code of all sitemap.xml URLs in parallel

$curl -s https://example.com/sitemap.xml | grep -oP '(?<=<loc>)[^<]+' | xargs -P 8 -I{} curl -o /dev/null -s -w '%{http_code} %{url_effective}\n' {} | grep -v '^200 ' | sort
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.