Quick access

Saved in this browser. Sign in to keep it on all your devices.

HTTP Status Codes

All 70 status codes you are likely to meet, from 100 Continue to 511, plus the nginx and Cloudflare codes, each with what it means in plain English.

1xx Informational

The request was received and is still being processed. Browsers handle these on their own, so you rarely see them.

100 Continue
The server got the request headers and the client can send the body. Used before uploading a large body with "Expect: 100-continue".
101 Switching Protocols
The server agrees to switch protocols, most often from HTTP to WebSocket.
102 Processing
A WebDAV server is still working on a long request. Deprecated and rarely sent today.
103 Early Hints
Sent before the final response with Link headers, so the browser can start loading CSS, fonts or scripts early.

2xx Success

The request worked.

200 OK
The standard success response. The body holds the page or data that was asked for.
201 Created
A new resource was created, usually after a POST. The Location header should point to it.
202 Accepted
The request was accepted but will be processed later, for example by a background job.
203 Non-Authoritative Information
A proxy changed the response it got from the origin server.
204 No Content
It worked and there is nothing to send back. Common after a DELETE or a save.
205 Reset Content
It worked; the client should clear the form it sent.
206 Partial Content
Only part of the file is sent, as asked by a Range header. Used to resume downloads and stream video.
207 Multi-Status
WebDAV: the body lists a separate status for each of several resources.
208 Already Reported
WebDAV: members of this collection were already listed earlier in the same reply.
226 IM Used
The server returned the changes to a resource (delta encoding) rather than the whole thing.

3xx Redirection

The client has to go somewhere else, given in the Location header, or use its cached copy.

300 Multiple Choices
There are several versions of the resource to choose from. Rarely used.
301 Moved Permanently
The URL has moved for good. Browsers and search engines switch to the new address and pass rankings to it.
302 Found
A temporary redirect. Search engines keep the old URL. Browsers may turn a POST into a GET when they follow it.
303 See Other
Go to another URL with a GET. Used after a form POST so that refreshing the page does not send the form again.
304 Not Modified
The copy the browser already has is still current, so no body is sent. Saves bandwidth on repeat visits.
307 Temporary Redirect
Like 302, but the method and body must stay the same: a POST stays a POST.
308 Permanent Redirect
Like 301, but the method and body must stay the same. Safe for API endpoints that move.

4xx Client Error

Something is wrong with the request itself: the address, the login, the data sent, or how often it was sent.

400 Bad Request
The server cannot read the request: broken JSON, a missing field, or a malformed header.
401 Unauthorized
You are not logged in, or the token or API key is missing, wrong or expired.
402 Payment Required
Reserved for payments. Some APIs send it when a plan has run out or a payment failed.
403 Forbidden
The server knows who you are but will not let you in: no permission, a blocked IP, or a firewall rule.
404 Not Found
Nothing exists at this address. The link is wrong, or the page was moved or deleted.
405 Method Not Allowed
The URL exists but not for this method, such as a POST to a page that only accepts GET.
406 Not Acceptable
The server cannot reply in any format listed in the Accept header.
407 Proxy Authentication Required
Like 401, but it is a proxy between you and the server that wants the login.
408 Request Timeout
The client took too long to send the request, so the server closed the connection.
409 Conflict
The request clashes with the current state, such as an edit to something that changed in the meantime, or a duplicate.
410 Gone
The resource was deleted on purpose and will not come back. Search engines drop it faster than a 404.
411 Length Required
The server needs a Content-Length header that the request did not send.
412 Precondition Failed
A condition in the headers, such as If-Match, was not met, so nothing was changed.
413 Content Too Large
The upload or request body is bigger than the server allows.
414 URI Too Long
The URL is longer than the server accepts, often from a huge query string.
415 Unsupported Media Type
The body is in a format the server does not accept, such as XML sent to a JSON-only API.
416 Range Not Satisfiable
The Range header asks for bytes outside the file.
417 Expectation Failed
The server cannot meet the Expect header in the request.
418 I'm a teapot
An April Fools' joke from 1998 (RFC 2324). Some sites send it to turn away bots.
421 Misdirected Request
The request reached a server that cannot answer for this domain, which can happen when HTTP/2 connections are reused.
422 Unprocessable Content
The request is well formed but the data fails validation, such as an invalid email address. Common in APIs.
423 Locked
WebDAV: the resource is locked.
424 Failed Dependency
WebDAV: this action failed because an action it depended on failed.
425 Too Early
The server will not risk processing a request that might be replayed (TLS early data).
426 Upgrade Required
The client must switch to another protocol, given in the Upgrade header.
428 Precondition Required
The server insists on a conditional request (If-Match) to stop lost updates.
429 Too Many Requests
Rate limited: too many requests in a short time. The Retry-After header says how long to wait.
431 Request Header Fields Too Large
The headers are too big, often because of oversized cookies. Clearing the site's cookies usually fixes it.
451 Unavailable For Legal Reasons
Blocked for legal reasons, such as a court order or a government ban in your country.

5xx Server Error

The request looked fine, but the server, or a server behind it, failed to answer it.

500 Internal Server Error
A generic crash: an unhandled error in the site's code or configuration. The server log has the details.
501 Not Implemented
The server does not support the method or feature the request needs.
502 Bad Gateway
A proxy or load balancer got an invalid answer, or none, from the server behind it, which is often down or restarting.
503 Service Unavailable
The server is overloaded or down for maintenance. Usually temporary; Retry-After may say when to try again.
504 Gateway Timeout
A proxy waited too long for the server behind it, often because of a slow database query or script.
505 HTTP Version Not Supported
The server does not support the HTTP version of the request.
506 Variant Also Negotiates
A server configuration error in content negotiation.
507 Insufficient Storage
WebDAV: the server has run out of space to store what was sent.
508 Loop Detected
WebDAV: the server found an infinite loop while processing the request.
510 Not Extended
The request needs an extension the server does not have. Obsolete.
511 Network Authentication Required
You need to log in to the network first, as on hotel or airport Wi-Fi portals.

Unofficial codes

Not part of the HTTP standard, but sent by popular web servers and CDNs.

444 No Response (nginx)
nginx closed the connection without sending anything, usually to drop unwanted traffic. It only appears in nginx logs.
499 Client Closed Request (nginx)
The visitor or app gave up and closed the connection before nginx could answer. Logged by nginx only.
520 Web Server Returned an Unknown Error (Cloudflare)
The origin server sent Cloudflare an empty, unknown or unexpected response.
521 Web Server Is Down (Cloudflare)
The origin server refused Cloudflare's connection. The site's server is off or blocks Cloudflare's IP addresses.
522 Connection Timed Out (Cloudflare)
Cloudflare could not complete a connection to the origin server in time.
523 Origin Is Unreachable (Cloudflare)
Cloudflare cannot reach the origin, often because of wrong DNS records.
524 A Timeout Occurred (Cloudflare)
The origin accepted the connection but took longer than 100 seconds to reply.
525 SSL Handshake Failed (Cloudflare)
Cloudflare could not agree on a secure connection with the origin server.
526 Invalid SSL Certificate (Cloudflare)
The origin server's certificate is expired, self-signed or for another name, and Cloudflare is set to check it.
Version 1.1 Updated What's new

Release notes

  1. v1.1 Latest
    • Added an in-depth guide below the tool, written from what the tool actually does.
    • The list now covers 70 codes, each with a plain-English meaning, including common nginx and Cloudflare codes.
    • Search now filters single codes, and every code has its own link.

About the HTTP Status Codes

Every HTTP response starts with a three-digit status code. The first digit gives the class: 1xx information, 2xx success, 3xx redirect, 4xx client error, and 5xx server error.

How to use it

  1. 1 Search for a code or a word such as "redirect".
  2. 2 Read what it means and when servers send it.
  3. 3 Use the right code in your API or server.

Frequently asked questions

What is the difference between 301 and 302?

301 is a permanent redirect, so search engines move rankings to the new URL. 302 is temporary, so the old URL keeps its rankings.

What is the difference between 401 and 403?

401 means you are not authenticated (log in first). 403 means you are logged in but not allowed to access the resource.

What does a 503 error mean?

The server is temporarily unavailable, often because of maintenance or overload. Clients can retry later.

Picking the right code for an API response

Clients decide what to do from the status code before they read the body, so a precise code saves everyone time:

  • 201 after creating something, with a Location header pointing to it; 204 when there is nothing to return.
  • 400 when the request cannot be read at all; 422 when it can be read but a field fails validation.
  • 401 when no valid login or token was sent; 403 when the caller is known but not allowed.
  • 404 for an id that does not exist; 410 for something deleted on purpose.
  • 409 when the change clashes with the current state, such as a username that is already taken.
  • 429 with a Retry-After header when a client goes over its rate limit.

Avoid answering an error with 200 and a message such as {"error": true} in the body. Monitoring tools, caches and client libraries all treat a 200 as success, so the failure goes unnoticed.

Redirects and search rankings

Use 301 or 308 when a page has moved for good, for example after changing your URL structure or moving from http to https. Search engines transfer the old page’s rankings to the new address and, over time, show only the new one. Use 302 or 307 for short-lived moves, such as sending visitors to a sale page for a week.

The difference between the two pairs is the method. A browser may follow a 301 or 302 with a GET even if the original request was a POST, while 307 and 308 keep the method and body. For API endpoints that move, 308 is the safe choice.

Keep redirect chains short. Each hop adds a round trip, and crawlers may stop following after several. Point old URLs straight at their final destination instead of through a list of older ones.

Telling 502, 503 and 504 apart

All three come from a proxy, load balancer or CDN that sits in front of the application, and each points to a different cause:

  • 502 Bad Gateway: the application server sent nothing usable. It has crashed, is restarting, or the proxy points to the wrong port.
  • 503 Service Unavailable: the server is up but refusing work, during maintenance or when every worker is busy.
  • 504 Gateway Timeout: the application accepted the request but did not finish in time, usually because of a slow database query or an external API that hangs.

A 500, by contrast, comes from the application itself and means its code threw an error. The server’s error log names the line.

Soft 404s and other mistakes search engines notice

A “soft 404” is a page that says “not found” or shows an empty search but returns 200. Google treats it as missing anyway and reports it in Search Console, while the page wastes crawl time. Return a real 404 or 410 for pages that no longer exist, and redirect only when there is a close replacement, not to the home page.

For planned downtime, send 503 with a Retry-After header rather than a maintenance page with 200. Crawlers then come back later instead of indexing the maintenance message.

Use the search box above to filter the list by number or by any word in a description, such as “timeout” or “cache”. Each code also has its own link, so you can share the address of a single entry, such as #429.