HTTP status checker

Check response status and redirects for several URLs. Useful after a deployment or a link migration.

URLs to check (one per line, up to 5)

Quick start

Enter one URL per line.
Check up to five URLs.
Compare status codes and final destinations.

Status codes

Code	Meaning	Next check
200	The HTTP request was handled successfully	Confirm the expected content and function.
301 / 302 / 307 / 308	Redirect	Check Location and the final URL.
401 / 403	Authentication required or access denied	Check credentials, permissions, and WAF rules.
404	The requested resource was not found	Check the path and deployment.
429	Request limit	Check Retry-After and rate limits.
500 / 502 / 503 / 504	Server or upstream failure	Compare application and proxy logs.

HTTP errors versus connection failures

An HTTP status exists only after an HTTP response is received. DNS failure, refused TCP connections, TLS failures, and timeouts are separate from 404 or 500.

This tool follows up to 2 HTTP redirects per URL. It does not execute JavaScript redirects, use login cookies, or validate page content.

Troubleshooting order

Check the scheme, hostname, and case-sensitive path.
Review the final host and path after redirects.
Check whether authentication is required.
Compare proxy and application logs at the same time.

Comparing results for different forms of an address

Requests reach the same site through old addresses, different letter case or a missing trailing slash. Check that each form leads to the intended final address. The output below checks PPORT’s own addresses.

Measured output · PPORT operator’s PC (Git Bash, curl 8.21.0) · 2026-10-13

$ curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' https://pport.cloud/ja/about
301 https://pport.cloud/en/about
$ curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' https://pport.cloud/KO/
404
$ curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' https://nonexistent.invalid/
000

Result	How to read it
301 → /en/about	A permanent redirect: the address of a retired language goes to the English page with the same path.
404 (/KO/)	Paths are case-sensitive. /ko/ exists but /KO/ does not. If uppercase links circulate elsewhere, add a separate redirect.
000	No HTTP response was received. .invalid is a top-level domain reserved never to exist, so name resolution failed (curl exit code 6).

Checking a site after moving it

List the old addresses, starting with those that bring the most traffic from search results and external links.
Check them with this tool, five at a time, and confirm that each one reaches the new address with 301 or 308.
Confirm that the final address returns 200 and that there is no chain of two or more redirects. This tool follows up to two redirects, so it cannot show the end of a longer chain.
Keep only final addresses that return 200 without a redirect in the sitemap.

Frequently asked questions

Does 200 mean the service is healthy?

No. An error page or a login screen can return 200. Test the expected content and feature separately.