HTTP Status Codes – Complete List with Meanings

Searchable list of all HTTP status codes (1xx to 5xx) with plain-English explanations: 200, 301, 302, 304, 400, 401, 403, 404, 429, 500, 502, 503 and more.

Free, no sign-up
Runs in your browser, nothing uploaded

1xx Informational – The request was received and is continuing.

100Continue

The server received the request headers; the client can send the body. Used with an Expect: 100-continue header before large uploads.

101Switching Protocols

The server is switching protocols as the client asked, most often when upgrading an HTTP connection to a WebSocket.

103Early Hints

Sent before the final response so the browser can start preloading resources (via Link headers) while the server prepares the page.

2xx Success – The request was received, understood and accepted.

200OKCommon

The request succeeded. For GET, the body contains the resource; for POST, the result of the action.

201CreatedCommon

The request succeeded and a new resource was created. The Location header usually points to it. Typical response to a successful POST.

202Accepted

The request was accepted for processing, but processing hasn't finished, as with queued background jobs.

203Non-Authoritative Information

The returned content was modified by a transforming proxy and isn't exactly what the origin server sent.

204No ContentCommon

The request succeeded and there's no body to return. Common for DELETE requests and saves that don't return data.

205Reset Content

The request succeeded and the client should reset the document view, for example clear a form.

206Partial Content

The server is returning only part of the resource because the client sent a Range header. Used for resumable downloads and video streaming.

207Multi-Status

WebDAV: the body contains separate status codes for multiple operations.

208Already Reported

WebDAV: members of a collection were already listed earlier in the same response.

226IM Used

The server applied instance manipulations (delta encoding) to the resource.

3xx Redirection – Further action (usually following a redirect) is needed.

300Multiple Choices

There are several representations of the resource and the client or user should pick one. Rarely used.

301Moved PermanentlyCommon

A permanent redirect: the resource has a new URL, given in the Location header. Search engines transfer ranking signals to the new URL. Use it for site migrations and changed URLs.

302FoundCommon

A temporary redirect: the resource is at another URL for now. Browsers usually follow it with a GET request. Use 307 if the method must be preserved.

303See Other

The client should GET another URL. Typically used after a form POST to redirect to a result page (the Post/Redirect/Get pattern).

304Not ModifiedCommon

The cached copy is still valid (the client sent If-None-Match or If-Modified-Since), so there's no body. Saves bandwidth.

307Temporary Redirect

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

308Permanent Redirect

Like 301, but the method and body must not change. Good for permanently moving API endpoints that receive POST requests.

4xx Client error – The request has a problem on the client's side.

400Bad RequestCommon

The server can't process the request because of a client error, such as malformed JSON, invalid parameters or a bad header.

401UnauthorizedCommon

Authentication is required and has failed or wasn't provided. The client should log in or send valid credentials. Despite the name, it means unauthenticated.

402Payment Required

Reserved for future use. Some APIs use it when a payment or subscription is needed.

403ForbiddenCommon

The server understood the request but refuses it. Unlike 401, logging in won't help: the user doesn't have permission.

404Not FoundCommon

The server can't find the requested resource. The URL may be wrong, or the page was removed. Search engines eventually drop 404 pages from their index.

405Method Not Allowed

The HTTP method isn't supported for this URL, for example a POST to a read-only endpoint. The Allow header lists the supported methods.

406Not Acceptable

The server can't produce a response in any format listed in the request's Accept headers.

407Proxy Authentication Required

Like 401, but the client must authenticate with a proxy first.

408Request Timeout

The server timed out waiting for the client to finish sending the request.

409ConflictCommon

The request conflicts with the current state of the resource, such as an edit conflict or a duplicate record.

410Gone

The resource was deliberately and permanently removed, with no forwarding address. Search engines may drop it faster than a 404.

411Length Required

The server requires a Content-Length header.

412Precondition Failed

A condition in the request headers, such as If-Match, wasn't met. Used to prevent overwriting changes made by someone else.

413Content Too Large

The request body is larger than the server allows, for example an upload over the size limit (in nginx, client_max_body_size).

414URI Too Long

The URL is longer than the server will process, often caused by too much data in the query string.

415Unsupported Media Type

The request body's format (Content-Type) isn't supported, for example XML sent to a JSON-only API.

416Range Not Satisfiable

The Range header asks for a part of the file that doesn't exist.

417Expectation Failed

The server can't meet the requirement in the Expect header.

418I'm a teapot

An April Fools' joke from RFC 2324 (Hyper Text Coffee Pot Control Protocol). Some servers return it as an easter egg.

421Misdirected Request

The request reached a server that can't respond for this host, which can happen with reused HTTP/2 connections.

422Unprocessable ContentCommon

The request is well-formed but its content is invalid, for example validation errors on a form or API input.

423Locked

WebDAV: the resource is locked.

424Failed Dependency

WebDAV: the request failed because a previous request it depended on failed.

425Too Early

The server won't process a request that might be replayed (sent in TLS early data).

426Upgrade Required

The client must switch to a different protocol, given in the Upgrade header.

428Precondition Required

The server requires conditional requests (such as If-Match) to prevent lost updates.

429Too Many RequestsCommon

The client has sent too many requests in a given time (rate limiting). The Retry-After header may say when to try again.

431Request Header Fields Too Large

The headers are too large, often because of oversized cookies.

451Unavailable For Legal Reasons

The resource can't be provided for legal reasons, such as a court order or government censorship.

5xx Server error – The server failed to fulfil a valid request.

500Internal Server ErrorCommon

A generic server error: something unexpected went wrong, such as an unhandled exception. Check the server logs.

501Not Implemented

The server doesn't support the functionality needed for the request, such as an unknown HTTP method.

502Bad GatewayCommon

A gateway or proxy (such as nginx or a load balancer) got an invalid response from the server behind it. Often the app server crashed or isn't running.

503Service UnavailableCommon

The server is temporarily unable to handle the request because of overload or maintenance. Retry-After may say when it'll be back.

504Gateway TimeoutCommon

A gateway or proxy didn't get a response from the server behind it in time. Often a slow database query or an overloaded backend.

505HTTP Version Not Supported

The server doesn't support the HTTP version used in the request.

506Variant Also Negotiates

A server configuration error in content negotiation.

507Insufficient Storage

WebDAV: the server can't store what's needed to complete the request.

508Loop Detected

WebDAV: the server detected an infinite loop while processing the request.

511Network Authentication Required

The client needs to authenticate to get network access, as with Wi-Fi captive portals in hotels and airports.

About the HTTP Status Codes

Look up any HTTP response status code and what it means, from 100 Continue to 511 Network Authentication Required. Search by number or name and filter by class.

Key features

Every standard HTTP status code
Plain-English explanations
Search by number or name
Filter by class (2xx, 3xx, 4xx, 5xx)
Common codes highlighted
SEO notes for redirects and errors

HTTP status codes explained

Every response from a web server starts with a three-digit status code. The first digit tells you the class of response:

Class	Meaning
1xx	Informational: the request is in progress
2xx	Success: the request worked
3xx	Redirection: go somewhere else
4xx	Client error: the request has a problem
5xx	Server error: the server failed

Status codes and SEO

Code	Effect on search engines
200	Page can be indexed
301 / 308	Rankings pass to the new URL
302 / 307	Original URL stays indexed
404 / 410	Page is dropped from the index
5xx	Crawling slows down; long outages can cause pages to drop

A "soft 404", where a missing page returns 200 with a "not found" message, wastes crawl budget. Return a real 404 status instead.

Robots.txt tester, meta tag checker, and URL parser.

How to use the HTTP Status Codes

Enter your value in the fields above, or start from one of the examples or presets.
Results update instantly as you type.
Read the breakdown to understand each part of the result.
Copy what you need with the copy buttons. Everything runs in your browser.

Frequently asked questions

What's the difference between 301 and 302 redirects?

301 means the page has moved permanently, so search engines transfer rankings to the new URL. 302 means a temporary move, so the original URL keeps its place in search results. Use 301 for permanent URL changes.

What's the difference between 401 and 403?

401 Unauthorized means you need to log in (or your credentials are invalid). 403 Forbidden means you're identified but don't have permission, so logging in again won't help.

What causes a 502 Bad Gateway error?

A proxy or load balancer, such as nginx or Cloudflare, couldn't get a valid response from the application server behind it. Usually the app crashed, is restarting or isn't listening on the expected port.

Is 404 or 410 better for deleted pages?

Both remove the page from search results eventually. 410 Gone states the removal is permanent, so search engines may drop the page a little sooner.

Is my code uploaded anywhere?

No. Every developer tool runs entirely in your browser, so source code, configuration files and passwords never leave your device.

Which formatter do you use?

HTML, CSS and JavaScript are formatted with Prettier, the most widely used code formatter, so the output matches what most projects use. SQL uses sql-formatter, and minification uses Terser and CSSO.

Is there a size limit?

There's no fixed limit. Very large files (several megabytes) can take a few seconds, depending on your device.

Last updated: October 23, 2026

Related Dev tools

Bcrypt GeneratorNEW

Generate bcrypt password hashes with a chosen cost factor and verify a password against an existing bcrypt hash, entirely in your browser.

HTML FormatterNEW

Format and beautify messy or minified HTML with proper indentation, including embedded CSS and JavaScript. Powered by Prettier.

CSS FormatterNEW

Beautify minified or messy CSS, SCSS and Less with one rule per line and consistent indentation. Powered by Prettier.

JavaScript FormatterNEW

Format and beautify JavaScript, JSX and TypeScript code with Prettier. Choose indentation, line width, quotes and semicolons.

SQL FormatterNEW

Format SQL queries for MySQL, PostgreSQL, SQL Server, Oracle, SQLite, BigQuery and more, with uppercase keywords and clean indentation.

XML FormatterNEW

Format, validate and minify XML online. Pretty print with your choice of indentation, check for errors and remove comments.

YAML ValidatorNEW

Validate YAML and find syntax errors with line and column numbers, then reformat it with consistent indentation. Great for Docker Compose, Kubernetes and CI files.

YAML to JSONNEW

Convert YAML to JSON instantly, including multi-document YAML files. Choose pretty-printed or minified JSON output.

1xx Informational – The request was received and is continuing.

2xx Success – The request was received, understood and accepted.

3xx Redirection – Further action (usually following a redirect) is needed.

4xx Client error – The request has a problem on the client's side.

5xx Server error – The server failed to fulfil a valid request.

About the HTTP Status Codes

Key features

HTTP status codes explained

Status codes and SEO

Related tools

How to use the HTTP Status Codes

Frequently asked questions

Related Dev tools

Bcrypt GeneratorNEW

HTML FormatterNEW

CSS FormatterNEW

JavaScript FormatterNEW

SQL FormatterNEW

XML FormatterNEW

YAML ValidatorNEW

YAML to JSONNEW

1xx Informational – The request was received and is continuing.

2xx Success – The request was received, understood and accepted.

3xx Redirection – Further action (usually following a redirect) is needed.

4xx Client error – The request has a problem on the client's side.

5xx Server error – The server failed to fulfil a valid request.