Skip to content
QuickStatus.dev

Free tools / HTTP status checker

HTTP status code checker

Paste up to 20 URLs, one per line. See the status code each one returns, the redirect chain it took to get there, whether HTTP upgrades to HTTPS, whether the final response sends HSTS, and how many days are left on the SSL certificate.

URLs

up to 20

A line without a scheme is checked as https://. Start a line with http:// to test the upgrade to HTTPS. Checked from Ashburn, Virginia (AWS us-east-1), with no cookies.

Request method

GET matches a browser. HEAD matches curl -I. Some servers answer HEAD with 405 or 404 while GET returns 200.

How the HTTP status checker works

Each URL is requested from Ashburn, Virginia (us-east-1) with a plain client: no cookies, no stored HTTPS-only policy, and a QuickStatusPing user agent. The checker reads the status line, follows Location on 301, 302, 303, 307, and 308, and stops at 10 hops or at the first URL that repeats. The status in the table is the last response in the chain.

Response time is DNS lookup, connect, TLS handshake, and time to first byte, added up across every hop. A URL that redirects once pays that cost twice. The body is not downloaded, so a slow page with a fast first byte still looks fast here. The number is measured from US East: a server in Europe or Asia will look slower from here than it does for its local users.

The lines are checked at the same time, so 20 URLs take about as long as the slowest one. Each URL gets 8 seconds. A host that resolves to a private or local address is not requested.

For the full headers on one URL, open it in the redirect checker. Every row links there.

HTTP status codes and what they mean

The first digit is the class. 2xx is success, 3xx is a redirect, 4xx is a problem with the request, and 5xx is a problem on the server. These are the codes you will see most often.

CodeNameWhat it usually means
200OKThe page loaded. Check the content too: an error page served with 200 is a soft 404.
204No ContentSuccess with an empty body. Common on API health endpoints and tracking pixels.
301Moved PermanentlyThe URL moved for good. Search engines move ranking to the target. The right code for HTTP to HTTPS and for an old slug.
302FoundA temporary redirect. Search engines keep the original URL. Often used by mistake for a permanent move.
304Not ModifiedThe cached copy is still good. This checker sends no cache headers, so it should not see one.
307 / 308Temporary / Permanent RedirectLike 302 and 301, but the method and body stay the same. A POST stays a POST.
400Bad RequestThe server could not parse the request. A malformed query string or an oversized cookie.
401UnauthorizedThe URL needs credentials. Normal for an API or an admin path.
403ForbiddenThe server answered and refused this client. Often a WAF or bot rule. The site can still be up. See When 403 means up.
404Not FoundNothing at this path. Fix the internal links or redirect the old URL with a 301.
405Method Not AllowedThe path exists but not for this method. Try GET if HEAD returns 405.
410GoneRemoved on purpose. Search engines drop a 410 faster than a 404.
429Too Many RequestsRate limited. Look for a Retry-After header.
500Internal Server ErrorThe application threw an error. Check the server logs for this path.
502Bad GatewayA proxy or CDN reached the origin and got a bad answer, or none.
503Service UnavailableThe server is overloaded or in maintenance. Usually temporary.
504Gateway TimeoutThe proxy gave up waiting for the origin. A slow database or a hung worker.

No status at all means the request failed before the server answered: the name did not resolve, the connection was refused, the TLS handshake failed, or the request timed out. The table names which one.

What the HTTPS column checks

Why a URL can return a different status somewhere else

This check runs from one place, Ashburn, Virginia. A CDN can serve a cached 200 in one region while another region gets a 502 from the origin. A bot rule can return 403 to a data-center IP and 200 to a home connection. A geo rule can redirect one country and not another. When a status here does not match what users report, run the website down checker. It requests the same URL from 16 locations at once.

Checking many URLs from the terminal

With curl and a file with one URL per line:

xargs -n1 -P8 curl -s -o /dev/null -L --max-redirs 10 --max-time 10 \
  -w '%{http_code} %{num_redirects} %{url_effective}\n' < urls.txt

-L follows redirects, %{num_redirects} counts them, and -P8 runs eight at a time. Drop -L to see the first status instead of the last.

Frequently asked questions

How do I check the HTTP status code of a URL?
Paste the URL above and press Check status. The table shows the final status code, the chain of codes before it (for example 301 → 200), and the time it took. From a terminal, curl -sI https://example.com prints the status line of one response.
Can I check more than 20 URLs?
Run them 20 at a time. There is a limit of 40 URLs per minute from one address, and a lower one per site, so the tool cannot be aimed at someone else's server. For a full site crawl, use the terminal command above or a crawler such as Screaming Frog.
Why does the checker show 403 when the page opens in my browser?
The server, its CDN, or a WAF is blocking requests that come from a cloud IP or that send no cookies. The host is up and answering. If you own the site and want monitoring to see 200, allow the monitor's user agent or IPs in the bot rule.
What is the difference between an HTTP and an HTTPS status check?
The status codes are the same. An HTTPS check also has to pass the TLS handshake, so an expired or mismatched certificate fails it before any status code exists. This checker reports both: the status code, and whether HTTPS, HSTS, and the certificate are in order.
Does a 3xx status mean the page is broken?
No. One redirect, such as HTTP to HTTPS or the bare domain to www, is normal. Two or more in a row slow the first load and usually mean two rules both rewrite the URL. A chain that never ends is a redirect loop. See Too many redirects.
Can I get an alert when a URL stops returning 200?
Yes. A QuickStatus.dev Website or API check requests the URL on a schedule, as often as every minute from up to five regions on Pro, and alerts by email, Slack, Discord, PagerDuty, or webhook. An API check expects an exact code, 200 by default, so it can also catch a 301 that turned into a 302. A certificate that stops verifying fails the check.

Know when a status code changes

This page checks your URLs once. QuickStatus.dev keeps checking them, from up to five regions, waits for the confirmation period you set so one bad response does not page you, and alerts when the status code or the certificate breaks. Free for 10 checks.