Free Tools / HTTP Response Code Check
HTTP Response Code Check
Enter a URL to see its HTTP status code, the full redirect chain, response headers and timing. Checked from Upzilla’s servers, no login needed.
Enter a URL to see its HTTP status code, the full redirect chain, response headers and timing. Checked from Upzilla’s servers, no login needed.
Status codes are grouped by their first digit. Here are the ones you will meet most often, and what to do about the errors.
| Code | Name | Meaning |
|---|---|---|
| 200 | OK | The request succeeded and the server returned the page or resource. |
| 301 | Moved Permanently | The URL has moved permanently. Browsers and search engines should use the new address. |
| 302 | Found (temporary redirect) | The URL is temporarily at another address. Search engines keep the original URL indexed. |
| 304 | Not Modified | The cached copy is still valid, so no body was sent. |
| 307 | Temporary Redirect | Like 302 but the request method must not change. |
| 308 | Permanent Redirect | Like 301 but the request method must not change. |
| 400 | Bad Request | The server could not understand the request, usually because of malformed syntax. |
| 401 | Unauthorized | Authentication is required and was missing or invalid. |
| 403 | Forbidden | The server understood the request but refuses to allow it. |
| 404 | Not Found | The server cannot find the requested page. |
| 410 | Gone | The page was removed on purpose and will not come back. |
| 429 | Too Many Requests | The client sent too many requests in a given time (rate limiting). |
| 500 | Internal Server Error | The server hit an unexpected condition and could not complete the request. |
| 502 | Bad Gateway | A gateway or proxy got an invalid response from the upstream server. |
| 503 | Service Unavailable | The server is temporarily unable to handle the request, often because of overload or maintenance. |
| 504 | Gateway Timeout | A gateway or proxy timed out waiting for the upstream server. |
Codes with a link have a detailed explanation page.
A three-digit number the server sends with every response to say how the request went. 2xx means success, 3xx a redirect, 4xx a client-side error such as a missing page, and 5xx a server-side error.
A 301 says the move is permanent, so search engines transfer signals to the new URL. A 302 says it is temporary, so the original URL stays in the index. Use 301 for permanent changes.
Every hop adds a full round trip, so the page loads slower, and search engines may stop following long chains. Point links straight at the final URL.
Some sites treat automated requests differently: bot protection, geo rules, cookies or a login can change the response. Try the GET method, and remember the check runs from our servers, not from your network.
HEAD asks for headers only and is lighter, but a few servers answer HEAD differently (for example with 405). GET is what browsers use, so it is the more realistic test.
Yes. An HTTP(S) monitor in Upzilla checks the URL on a schedule, verifies the status code you expect and alerts you when it changes.
Upzilla checks status codes on a schedule from several locations and alerts you when they change. 10 monitors free.