HTTP Status Code Reference

Look up every HTTP status code from 100 to 511. Searchable reference with plain-English explanations, category filters, and copy-to-clipboard.

100% client-side. Your data never leaves your browser.

1xx Informational

(4)

2xx Success

(10)

3xx Redirection

(7)

4xx Client Error

(29)

5xx Server Error

(11)
61 of 61 status codes

Converters & Examples

Which HTTP Status Code Should I Use? A Decision Guide

An interactive decision guide for choosing the right HTTP status code for your API. Covers success, redirect, client error, and server error responses with real-world examples.

Related Tools

%20
URL Encoder & HTML Entity Encoder

Encode text for URLs with encodeURIComponent or encodeURI, and escape HTML special characters to named or numeric entities. All processing happens in your browser.

 jwt
JWT Decoder

Decode and inspect JSON Web Tokens in your browser. View the header, payload claims, and expiration status without sending your token to any server.

 sha
Hash Generator

Generate MD5, SHA-1, SHA-256, and SHA-512 hashes from text or files. Uses the browser's Web Crypto API for SHA hashes with a pure JS fallback for MD5.

HTTP Status Code Reference

HTTP status codes are three digit numbers returned by a server in response to a client request. The first digit defines the category: 1xx for informational, 2xx for success, 3xx for redirection, 4xx for client errors, and 5xx for server errors. Every web developer and API consumer encounters these codes daily, and knowing what they mean saves debugging time.

How to Use

  1. Search by number or name. Type a status code like “404” or a keyword like “redirect” to filter the list
  2. Filter by category. Click a category tab to show only informational, success, redirection, client error, or server error codes
  3. Expand a code. Click any status code row to see a detailed explanation
  4. Copy. Click the copy button to copy the code and name to your clipboard

Understanding HTTP Status Code Categories

1xx Informational

Interim responses. The server has received the request and the client should continue or wait. You rarely see these directly. The most practical one is 101 Switching Protocols, which is how HTTP upgrades to WebSocket.

2xx Success

The request was received, understood, and accepted. 200 OK is the standard success response. 201 Created is the correct response for a POST that creates a new resource. 204 No Content is what you return for a successful DELETE when there is nothing to send back. Using the right 2xx code makes APIs self documenting.

3xx Redirection

Further action is needed to complete the request, usually following a Location header. 301 and 308 are permanent redirects (search engines transfer ranking). 302 and 307 are temporary (search engines keep the original URL). The difference between the paired codes: 307/308 guarantee method preservation, while 301/302 allow browsers to change POST to GET.

4xx Client Error

The request contains bad syntax or cannot be fulfilled. These are the caller’s fault. 400 Bad Request covers malformed input. 401 is for missing or invalid credentials. 403 is for valid credentials that lack permission. 404 is the universal “not found.” 422 is for valid syntax that fails business validation (common in REST APIs). 429 is rate limiting.

5xx Server Error

The server failed to fulfill a valid request. These are the server’s fault. 500 is the general purpose error. 502 and 504 point to proxy/gateway issues (the app server behind the proxy crashed or timed out). 503 means the server is temporarily overloaded or down for maintenance.

When debugging API integrations, start by checking whether the status code is a 4xx (fix your request) or a 5xx (check the server). Need to inspect a JWT that came back with a 401? Try the JWT Decoder. Building URLs for API requests? The URL Encoder handles percent encoding correctly.