DE

↑ ↓ select, Enter open, Esc close

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

harmlessSEO checksdebian, ubuntu
Adjust the values, the command updates live
user@server
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

Requests the homepage in all four combinations. Correct is exactly one variant with 200, while the other three redirect directly to it with 301. If several variants answer with 200, duplicate content is created and signals are split across multiple URLs.

Note: Status 000 usually means there is no DNS record or no valid certificate for that variant. The entry on redirect count and final target shows redirects that go through an intermediate step.

Also searched as

  • check www and non-www redirect
  • test http to https redirect
  • duplicate content www vs non-www
  • check all domain variants redirect

Related one-liners

All in SEO checks

Find mixed content in the HTML of an HTTPS page

$curl -s https://example.com/ | tr '\n' ' ' | grep -oiE '(src|srcset|data-src)="http://[^"]+"|<link[^>]+href="http://[^"]+"|url\(.?http://[^)]+\)' | sort -u
harmlessSEO checks

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

Follow and show the redirect chain of a URL

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

Show the redirect chain of a URL with status codes

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

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.