1. Home
  2. Developer
  3. HTTP Status Codes

HTTP Status Codes

Look up what 404, 500 and other HTTP status codes mean.

Runs in your browser · No upload
Numbers match from the first digit; names and descriptions are searched in both English and Korean.

1xx Informational (4)

100Continue

The request headers were accepted, so the client may go ahead and send the body. This is an interim response.

When you see it
Seen when a client sends `Expect: 100-continue` and waits for the server before uploading a large body.
RFC 9110 §15.2.1
101Switching Protocols

The server accepted an `Upgrade` request and is switching the protocol used on this connection.

When you see it
When opening a WebSocket, the HTTP connection is upgraded to WebSocket.
RFC 9110 §15.2.2
102Processing

An interim response saying the server has the request and is still working on it. It was dropped from RFC 4918 and is rarely used today.

When you see it
Used to keep a long-running WebDAV request from timing out.
RFC 2518 §10.1
103Early Hints

Sent before the final response, it uses `Link` headers to tell the browser which resources (CSS, JS) to preload.

When you see it
Lets the browser fetch assets while the server is still building the page.
RFC 8297 §2

2xx Success (10)

200OK

The request succeeded and the body carries the result. The exact meaning depends on the method (a resource for GET, the outcome for POST).

When you see it
Most normal page loads and API calls.
RFC 9110 §15.3.1 · Cacheable by default, without extra headers (RFC 9110).
201Created

The request succeeded and a new resource was created. The `Location` header usually holds its address.

When you see it
After a POST that creates a post, an account or another new record.
RFC 9110 §15.3.2
202Accepted

The request was received but processing is not finished, and there is no guarantee it will complete.

When you see it
When an asynchronous job such as a large conversion or a mail send was queued.
RFC 9110 §15.3.3
203Non-Authoritative Information

The request succeeded, but the content may be a modified copy made by a proxy rather than the origin server's own.

When you see it
Responses that passed through a transforming proxy.
RFC 9110 §15.3.4 · Cacheable by default, without extra headers (RFC 9110).
204No Content

The request succeeded and there is no body to send. Used when the page should stay as it is.

When you see it
Successful DELETE or PUT, autosave APIs, CORS preflight replies.
RFC 9110 §15.3.5 · Cacheable by default, without extra headers (RFC 9110).
205Reset Content

The request succeeded and the client should reset the view, such as a form, to its initial state. There is no body.

When you see it
To clear a form after it was submitted. Rarely used in practice.
RFC 9110 §15.3.6
206Partial Content

Only the bytes requested with a `Range` header were sent.

When you see it
Video seeking, resumed downloads, chunked downloads of large files.
RFC 9110 §15.3.7 · Cacheable by default, without extra headers (RFC 9110).
207Multi-Status

Carries separate results for several resources in a single XML body.

When you see it
WebDAV operations that touch many files at once.
RFC 4918 §11.1
208Already Reported

In WebDAV, the member was already listed earlier in the same `207` response and is not listed again.

When you see it
Skipping duplicate entries inside a `207` response.
RFC 5842 §7.1
226IM Used

The server answered a GET with the result of one or more instance manipulations such as delta encoding (RFC 3229).

When you see it
Special environments that support delta encoding. Almost never seen on the general web.
RFC 3229 §10.4.1

3xx Redirection (9)

300Multiple Choices

The resource has several representations to choose from. The server may point to its preferred one with `Location`, but there is no standard way to choose.

When you see it
Rarely used.
RFC 9110 §15.4.1 · Cacheable by default, without extra headers (RFC 9110).
301Moved Permanently

The resource has moved permanently. Use the address in `Location` from now on. Clients may change a POST into a GET when following it.

When you see it
Moving from http to https, domain migrations, URL restructuring.
RFC 9110 §15.4.2 · Cacheable by default, without extra headers (RFC 9110).
302Found

The resource is temporarily at another address. Keep using the original one. For historical reasons a POST may be changed into a GET.

When you see it
Redirect after login, sending visitors to a temporary maintenance page.
RFC 9110 §15.4.3
303See Other

Fetch the result of this request with a GET at the address in `Location`.

When you see it
The POST-Redirect-GET pattern: send the user to a result page after a form post so a refresh does not resubmit.
RFC 9110 §15.4.4
304Not Modified

For a conditional request (`If-None-Match`, `If-Modified-Since`) the resource has not changed, so use the cached copy. There is no body.

When you see it
When a browser revalidates its cache. It saves bandwidth.
RFC 9110 §15.4.5
305Use Proxy

It once told clients to go through the proxy in `Location`, but it is deprecated in RFC 9110 because of security concerns.

When you see it
Not used today, and browsers ignore it.
RFC 9110 §15.4.6
306(Unused)

A code from an old draft that is now only reserved. It is no longer used.

When you see it
You will not see it.
RFC 9110 §15.4.7
307Temporary Redirect

Like 302, but the client must repeat the request with the same method and body at the other address.

When you see it
Temporarily sending a POST elsewhere. Browsers also show 307 (Internal Redirect) when HSTS upgrades http to https by itself.
RFC 9110 §15.4.8
308Permanent Redirect

A permanent move like 301, but the request method and body must not change.

When you see it
Permanent moves where POST and PUT requests must reach the new address unchanged.
RFC 9110 §15.4.9 · Cacheable by default, without extra headers (RFC 9110).

4xx Client error (31)

400Bad Request

The server cannot or will not process the request because of something it sees as a client error, such as malformed syntax.

When you see it
Broken JSON, a bad query string, an oversized cookie.
How to fix
Visitor: Reload the page, and clear the site's cookies if it keeps happening.
Developer: Validate the body and headers, and explain the problem in the response body.
RFC 9110 §15.5.1
401Unauthorized

The request lacks valid credentials. The response must include `WWW-Authenticate` naming the scheme. Despite the name, this is about authentication.

When you see it
Not logged in, or the token is expired or invalid.
How to fix
Visitor: Log in, or log in again.
Developer: Send `WWW-Authenticate` and check token expiry. If the user is logged in but not allowed, use 403.
RFC 9110 §15.5.2
402Payment Required

Reserved for future use. It has no standardized meaning.

When you see it
Some payment and subscription APIs use it on their own to signal an unpaid plan or an exceeded quota.
RFC 9110 §15.5.3
403Forbidden

The server understood the request but refuses to authorize it. Authenticating again will not change the outcome.

When you see it
A page the logged-in user may not open, IP blocks, directory listing disabled.
How to fix
Visitor: Check that you are signed in with an account that has access, or ask the administrator.
Developer: Review permission rules, IP allow-lists and file permissions. To hide that a resource exists, 404 is an option.
RFC 9110 §15.5.4
404Not Found

The server found no resource at that address. It does not say whether this is temporary or permanent.

When you see it
A wrong URL, a deleted page, a typo.
How to fix
Visitor: Check the address for typos or use the site search.
Developer: Audit links and routes, and redirect moved pages with 301 or 308. Avoid soft 404s, where a missing page returns 200.
RFC 9110 §15.5.5 · Cacheable by default, without extra headers (RFC 9110).
405Method Not Allowed

The resource does not support that HTTP method. The response must list the allowed ones in an `Allow` header.

When you see it
A POST to a GET-only address, a DELETE on a read-only API.
How to fix
Visitor: Check the address, or try a different path.
Developer: Put the supported methods in `Allow` and check the route's method settings.
RFC 9110 §15.5.6 · Cacheable by default, without extra headers (RFC 9110).
406Not Acceptable

The server cannot produce a representation that matches the `Accept` headers of the request.

When you see it
The client accepts only `application/xml` but the server offers only JSON.
RFC 9110 §15.5.7
407Proxy Authentication Required

Like 401, but the client must authenticate with the proxy. The response carries a `Proxy-Authenticate` header.

When you see it
Networks that go through a corporate or school proxy.
RFC 9110 §15.5.8
408Request Timeout

The server did not receive a complete request in the time it was prepared to wait and closes the connection. The client may repeat the request.

When you see it
A request that stalled on a slow network, an idle connection.
How to fix
Visitor: Check your network and try again.
Developer: Review the server's request timeout and the proxy settings.
RFC 9110 §15.5.9 · Trying again later may succeed.
409Conflict

The request conflicts with the current state of the resource. It can be sent again after the conflict is resolved.

When you see it
A duplicate signup, a version clash from concurrent edits, a state change that was already applied.
How to fix
Visitor: Reload to see the latest content.
Developer: Explain the conflict in the body and detect concurrent edits by comparing ETags.
RFC 9110 §15.5.10
410Gone

The resource is no longer available and the server knows of no forwarding address. More deliberate than 404.

When you see it
A page removed on purpose, an event that has ended.
How to fix
Visitor: You will need to look for the information elsewhere.
Developer: Use it to make clear that the removal is intentional and permanent.
RFC 9110 §15.5.11 · Cacheable by default, without extra headers (RFC 9110).
411Length Required

The server requires a `Content-Length` header in the request.

When you see it
Sending a body without a length to a server that rejects chunked transfer.
RFC 9110 §15.5.12
412Precondition Failed

A condition in the request headers, such as `If-Match`, evaluated to false on the server, so the request was not performed.

When you see it
Updating a resource with `If-Match` after its ETag has changed (optimistic locking).
RFC 9110 §15.5.13
413Content Too Large

The request body is larger than the server is willing or able to process. Formerly called Payload Too Large.

When you see it
An upload over the size limit (for example nginx `client_max_body_size`).
How to fix
Visitor: Make the file smaller and upload again.
Developer: Check the upload limits of the server and any proxy, and show the maximum size in the UI.
RFC 9110 §15.5.14
414URI Too Long

The URI is longer than the server is willing to interpret.

When you see it
Too much data packed into a GET query, or a redirect loop that keeps growing the URL.
How to fix
Visitor: Shorten the address or start again from the beginning.
Developer: Send long data in a POST body and check for redirect loops.
RFC 9110 §15.5.15 · Cacheable by default, without extra headers (RFC 9110).
415Unsupported Media Type

The server does not support the format (`Content-Type`) or encoding of the request body.

When you see it
Sending `text/plain` to an API that accepts only JSON.
How to fix
Visitor: Check that the file type is supported.
Developer: Make sure the `Content-Type` header matches the body.
RFC 9110 §15.5.16
416Range Not Satisfiable

None of the ranges in the `Range` header overlap the resource.

When you see it
A resumed download that starts beyond the real file size.
RFC 9110 §15.5.17
417Expectation Failed

The server cannot meet the expectation given in the `Expect` header.

When you see it
A server or proxy that does not understand `Expect: 100-continue`.
RFC 9110 §15.5.18
418I'm a teapot

From RFC 2324 (the Hyper Text Coffee Pot Control Protocol, an April Fools' joke from 1998): a teapot cannot brew coffee. RFC 9110 and IANA keep it reserved as Unused.

When you see it
Easter eggs, or services that use it on their own to turn bots away.
RFC 2324 §2.3.2
421Misdirected Request

The request was directed at a server that is not able to produce a response for it.

When you see it
Reused HTTP/2 connections that mix hosts, or an SNI that does not match the Host header.
RFC 9110 §15.5.20
422Unprocessable Content

The syntax is correct but the instructions in the content cannot be processed. Formerly called Unprocessable Entity.

When you see it
APIs reporting validation failures such as a bad email format or a missing required field.
How to fix
Visitor: Check the values you entered.
Developer: Return errors per field in the body so users can fix them.
RFC 9110 §15.5.21
423Locked

In WebDAV, the resource being accessed is locked.

When you see it
A file that another user is editing.
RFC 4918 §11.3
424Failed Dependency

The request failed because another request it depended on failed (WebDAV).

When you see it
Several operations were sent together and an earlier one failed.
RFC 4918 §11.4
425Too Early

The server will not process a request sent in TLS 1.3 early data (0-RTT) because it might be replayed. Send it again after the handshake completes.

When you see it
An unsafe request arriving as early data behind a CDN or server that uses 0-RTT.
RFC 8470 §5.2 · Trying again later may succeed.
426Upgrade Required

The server will not perform the request with the current protocol. Retry using a protocol named in the `Upgrade` header.

When you see it
A server that requires a newer protocol, for example a higher TLS version.
RFC 9110 §15.5.22
428Precondition Required

The server requires the request to be conditional (for example with `If-Match`) to prevent lost updates from concurrent edits.

When you see it
Updating a resource without sending an ETag.
RFC 6585 §3
429Too Many Requests

The client sent too many requests in a given time. A `Retry-After` header may say how long to wait.

When you see it
API quota exceeded, login attempt limits, crawler throttling.
How to fix
Visitor: Wait a moment and try again.
Developer: Honour `Retry-After` and retry with exponential backoff. On the server side, expose the remaining quota in headers.
RFC 6585 §4 · Trying again later may succeed.
431Request Header Fields Too Large

The request headers, as a whole or one of them, are too large.

When you see it
Cookies have piled up and inflated the headers.
How to fix
Visitor: Clear the cookies for that site.
Developer: Shrink the cookies or review the server's header size limit.
RFC 6585 §5
444No Response(Unofficial · nginx)

An internal nginx code logged when the server closes the connection without sending a response. It never reaches the client.

When you see it
Silently dropping abusive requests with `return 444;`.
Not registered in the IANA registry.
451Unavailable For Legal Reasons

The server cannot provide the resource because of a legal demand such as a court order or censorship. The number nods to the novel Fahrenheit 451.

When you see it
Content blocked by a court order or a government block.
RFC 7725 §3
499Client Closed Request(Unofficial · nginx)

Logged by nginx when the client closes the connection before the server has answered.

When you see it
The user closed the page, or the client timeout fired first.
Not registered in the IANA registry.

5xx Server error (18)

500Internal Server Error

The server hit an unexpected condition that kept it from fulfilling the request. The most generic server error.

When you see it
Code exceptions, configuration errors, database connection failures.
How to fix
Visitor: Try again later, and tell the site operator if it persists.
Developer: Check the server logs. Do not expose internals or stack traces in the response.
RFC 9110 §15.6.1
501Not Implemented

The server does not support the functionality needed to fulfil the request, such as an unknown method. It may be added later.

When you see it
The server received an HTTP method it does not recognize.
How to fix
Visitor: Try another approach or another service.
Developer: Implement the method or use only supported ones. If the method is known but not allowed on that resource, use 405.
RFC 9110 §15.6.2 · Cacheable by default, without extra headers (RFC 9110).
502Bad Gateway

A gateway or proxy received an invalid response from the upstream server.

When you see it
The app server behind a reverse proxy (such as nginx) crashed or sent a broken reply.
How to fix
Visitor: Reload in a moment.
Developer: Check the health and logs of the app behind the proxy, and the upstream address settings.
RFC 9110 §15.6.3 · Trying again later may succeed.
503Service Unavailable

The server is overloaded or down for maintenance and cannot handle the request now. `Retry-After` may say when to come back.

When you see it
Maintenance windows, traffic spikes, a pause during deployment.
How to fix
Visitor: Try again in a little while.
Developer: During maintenance send 503 with `Retry-After` to signal that the outage is temporary.
RFC 9110 §15.6.4 · Trying again later may succeed.
504Gateway Timeout

A gateway or proxy timed out waiting for a response from the upstream server.

When you see it
A slow query or external API delay pushed the request past the proxy timeout.
How to fix
Visitor: Try again in a little while.
Developer: Optimize the slow work or adjust the proxy timeout. Handle long jobs asynchronously and answer 202.
RFC 9110 §15.6.5 · Trying again later may succeed.
505HTTP Version Not Supported

The server does not support the HTTP version used in the request.

When you see it
A request in a newer HTTP version sent to a very old server, or a malformed request line.
RFC 9110 §15.6.6
506Variant Also Negotiates

A misconfigured transparent content negotiation set-up led the server into a circular reference.

When you see it
A server configuration error that is almost never seen.
RFC 2295 §8.1
507Insufficient Storage

The server cannot store what is needed to complete the request (WebDAV).

When you see it
The disk is full and the file cannot be saved.
RFC 4918 §11.5
508Loop Detected

The server stopped processing because it found an infinite loop (WebDAV).

When you see it
Processing a collection that contains itself.
RFC 5842 §7.2
510Not Extended

The extensions required by the HTTP Extension Framework (RFC 2774) are missing from the request. Rarely used today.

When you see it
You will hardly ever see it.
RFC 2774 §7
511Network Authentication Required

The client must authenticate to gain network access.

When you see it
A captive portal on public Wi-Fi intercepts the request.
How to fix
Visitor: Open the Wi-Fi sign-in page in your browser and authenticate.
Developer: Captive portals should answer intercepted requests with 511 instead of 200 so clients can tell.
RFC 6585 §6
520Web Server Returned an Unknown Error(Unofficial · Cloudflare)

Cloudflare received an unexpected response from the origin server.

When you see it
The origin crashed or sent an empty reply or invalid headers.
How to fix
Visitor: Try again later, and tell the site operator if it persists.
Developer: Check the origin server logs and the size of its response headers.
Not registered in the IANA registry.
521Web Server Is Down(Unofficial · Cloudflare)

Cloudflare's connection to the origin server was refused.

When you see it
The origin is off, or a firewall blocks Cloudflare's IP addresses.
How to fix
Visitor: Wait for the site operator to restore it.
Developer: Check that the origin is running and its firewall allows Cloudflare IPs.
Not registered in the IANA registry.
522Connection Timed Out(Unofficial · Cloudflare)

Cloudflare could not establish a TCP connection to the origin server.

When you see it
The origin is overloaded, or there is a network path or firewall problem.
How to fix
Visitor: Try again in a little while.
Developer: Check origin load, firewall rules and the network path.
Not registered in the IANA registry.
523Origin Is Unreachable(Unofficial · Cloudflare)

Cloudflare could not reach the origin server.

When you see it
The origin IP in DNS is wrong, or there is a routing problem.
Not registered in the IANA registry.
524A Timeout Occurred(Unofficial · Cloudflare)

Cloudflare connected to the origin but got no response within the time limit (100 seconds by default).

When you see it
Requests that take very long.
How to fix
Visitor: Try again in a little while.
Developer: Move long-running work to an asynchronous job.
Not registered in the IANA registry.
525SSL Handshake Failed(Unofficial · Cloudflare)

The SSL/TLS handshake between Cloudflare and the origin server failed.

When you see it
The origin does not support TLS, or the cipher settings do not match.
Not registered in the IANA registry.
526Invalid SSL Certificate(Unofficial · Cloudflare)

Cloudflare could not validate the SSL certificate on the origin server.

When you see it
In Full (strict) mode when the origin certificate is expired or self-signed.
Not registered in the IANA registry.

How to use

  1. Type a code (404), the first digits (40), a class (4xx), an English name (not found) or a Korean word into the search box. With an empty box you get the whole list, grouped by class.
  2. Use the class buttons (1xx to 5xx) above to narrow the list.
  3. Click a code to open its meaning, when you see it, how to fix it (for visitors and for developers) and the RFC it comes from.
  4. Copy link copies an address such as #404 that opens that code directly, which is handy in team docs and issues.

Overview by class

Class Meaning Codes in this tool
1xx Informational: interim response, the request was received and work continues 4
2xx Success: the request was received and handled 10
3xx Redirection: more action is needed to complete the request 9
4xx Client error: something is wrong with the request itself 31
5xx Server error: the server failed to handle a valid request 18

The list covers the standard (IANA registry) codes plus a few unofficial ones you meet often (nginx 444 and 499, Cloudflare 520–526), and unofficial codes show their source. Names and meanings follow RFC 9110 (HTTP Semantics). Note that 413 was Payload Too Large and is now Content Too Large, and 422 changed from Unprocessable Entity to Unprocessable Content.

Codes that are easy to mix up

401 vs 403

Code Meaning Does logging in change it?
401 Credentials missing or invalid (WWW-Authenticate required) It can
403 The server knows who you are, but you are not allowed It does not

301, 302, 307, 308

Code Move Method
301 Permanent A POST may become a GET
302 Temporary A POST may become a GET
307 Temporary Kept as is
308 Permanent Kept as is

After a form post, 303 (always a GET) is the code for sending users to a result page.

404 vs 410: 404 only says nothing is there now and does not say whether that is permanent. 410 says the resource was removed on purpose and for good.

502, 503, 504: 502 means the upstream server sent a bad response, 503 means the server is overloaded or in maintenance and cannot serve the request, and 504 means the upstream server did not answer in time. All three are common behind a proxy or gateway.

The SEO angle

  • Use 301 or 308 when an address moves for good. If 302 or 307 stays in place for a long time, search engines may keep treating the old address as the main one.
  • A soft 404 is a page that shows a “not found” screen but sends status 200. Search engines can mistake the empty page for a real one, so a page that truly does not exist should return 404 or 410.
  • During maintenance send 503 with Retry-After to say the outage is temporary. If 5xx errors go on for a long time, pages can drop out of the index.

Codes that are safe to retry

This tool marks 408, 425, 429, 502, 503 and 504 as “trying again later may succeed”. 429 and 503 can carry a Retry-After header with a wait time (seconds or a date): honour it when present, otherwise back off exponentially (1 s, 2 s, 4 s and so on). 4xx codes that need the request itself to change, such as 400, 401, 403, 404 and 422, give the same answer however often you repeat them.

Codes that are cacheable by default (RFC 9110) are 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414 and 501, and the tool labels them.

418 is a joke from the April Fools’ RFC 2324 (1998) and is not recommended for real services.

Related tools: User-Agent Parser, URL Encoder, JSON Formatter, IP Subnet Calculator.

This tool runs entirely in your browser and your search text is never sent to a server.

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.