HTTP Status Code Lookup
Type a status code or a word to get its reason phrase, class, meaning, defining RFC section, default cacheability and common causes and fixes. The example, 404 Not Found, is a 4xx Client error defined in RFC 9110 §15.5.5; a cache may reuse it without explicit freshness headers (cacheable by default). The reference table lists all 63 codes in the IANA HTTP Status Code Registry, with 306 and 418 shown as reserved “(Unused)” numbers, not real codes. Everything runs in your browser and nothing you type is sent anywhere.
Updated Runs in your browser: nothing you enter is uploadedHow this tool works
404 Not Found
404 Not Found
- Class
- 4xx Client error
- Registry status
- Registered
- Defined in
- RFC 9110 §15.5.5
- Cacheable by default?
- Yes, by default
What it means
The server cannot find a current representation of the target, or does not want to say. It does not say whether the absence is temporary or permanent.
Common causes
- A mistyped, removed or renamed URL.
- A broken link or a case-sensitive path mismatch.
- A route that is not deployed.
Common fixes
- Check the URL and its case. Restore the page or add a 301 redirect to its new address.
- Use 410 if it is gone for good.
All registered status codes
The permanent entries of the IANA HTTP Status Code Registry. Filter by word, class or cacheability.
Showing all 63 registered codes.
| Code | Reason phrase | Class | Registry status | Defined in | Cacheable by default? |
|---|---|---|---|---|---|
| 100 | Continue | 1xx Informational | Registered | RFC 9110 §15.2.1 | No |
| 101 | Switching Protocols | 1xx Informational | Registered | RFC 9110 §15.2.2 | No |
| 102 | Processing | 1xx Informational | Obsolete | RFC 2518 §10.1 | No |
| 103 | Early Hints | 1xx Informational | Registered | RFC 8297 §2 | No |
| 200 | OK | 2xx Successful | Registered | RFC 9110 §15.3.1 | Yes, by default |
| 201 | Created | 2xx Successful | Registered | RFC 9110 §15.3.2 | Only with explicit freshness |
| 202 | Accepted | 2xx Successful | Registered | RFC 9110 §15.3.3 | Only with explicit freshness |
| 203 | Non-Authoritative Information | 2xx Successful | Registered | RFC 9110 §15.3.4 | Yes, by default |
| 204 | No Content | 2xx Successful | Registered | RFC 9110 §15.3.5 | Yes, by default |
| 205 | Reset Content | 2xx Successful | Registered | RFC 9110 §15.3.6 | Only with explicit freshness |
| 206 | Partial Content | 2xx Successful | Registered | RFC 9110 §15.3.7 | Yes, by default |
| 207 | Multi-Status | 2xx Successful | Registered | RFC 4918 §11.1 | Only with explicit freshness |
| 208 | Already Reported | 2xx Successful | Registered | RFC 5842 §7.1 | Only with explicit freshness |
| 226 | IM Used | 2xx Successful | Registered | RFC 3229 §10.4.1 | Only with explicit freshness |
| 300 | Multiple Choices | 3xx Redirection | Registered | RFC 9110 §15.4.1 | Yes, by default |
| 301 | Moved Permanently | 3xx Redirection | Registered | RFC 9110 §15.4.2 | Yes, by default |
| 302 | Found | 3xx Redirection | Registered | RFC 9110 §15.4.3 | Only with explicit freshness |
| 303 | See Other | 3xx Redirection | Registered | RFC 9110 §15.4.4 | Only with explicit freshness |
| 304 | Not Modified | 3xx Redirection | Registered | RFC 9110 §15.4.5 | No |
| 305 | Use Proxy | 3xx Redirection | Deprecated | RFC 9110 §15.4.6 | Only with explicit freshness |
| 306 | (Unused) | 3xx Redirection | Reserved, unused | RFC 9110 §15.4.7 | No |
| 307 | Temporary Redirect | 3xx Redirection | Registered | RFC 9110 §15.4.8 | Only with explicit freshness |
| 308 | Permanent Redirect | 3xx Redirection | Registered | RFC 9110 §15.4.9 | Yes, by default |
| 400 | Bad Request | 4xx Client error | Registered | RFC 9110 §15.5.1 | Only with explicit freshness |
| 401 | Unauthorized | 4xx Client error | Registered | RFC 9110 §15.5.2 | Only with explicit freshness |
| 402 | Payment Required | 4xx Client error | Registered | RFC 9110 §15.5.3 | Only with explicit freshness |
| 403 | Forbidden | 4xx Client error | Registered | RFC 9110 §15.5.4 | Only with explicit freshness |
| 404 | Not Found | 4xx Client error | Registered | RFC 9110 §15.5.5 | Yes, by default |
| 405 | Method Not Allowed | 4xx Client error | Registered | RFC 9110 §15.5.6 | Yes, by default |
| 406 | Not Acceptable | 4xx Client error | Registered | RFC 9110 §15.5.7 | Only with explicit freshness |
| 407 | Proxy Authentication Required | 4xx Client error | Registered | RFC 9110 §15.5.8 | Only with explicit freshness |
| 408 | Request Timeout | 4xx Client error | Registered | RFC 9110 §15.5.9 | Only with explicit freshness |
| 409 | Conflict | 4xx Client error | Registered | RFC 9110 §15.5.10 | Only with explicit freshness |
| 410 | Gone | 4xx Client error | Registered | RFC 9110 §15.5.11 | Yes, by default |
| 411 | Length Required | 4xx Client error | Registered | RFC 9110 §15.5.12 | Only with explicit freshness |
| 412 | Precondition Failed | 4xx Client error | Registered | RFC 9110 §15.5.13 | Only with explicit freshness |
| 413 | Content Too Large | 4xx Client error | Registered | RFC 9110 §15.5.14 | Only with explicit freshness |
| 414 | URI Too Long | 4xx Client error | Registered | RFC 9110 §15.5.15 | Yes, by default |
| 415 | Unsupported Media Type | 4xx Client error | Registered | RFC 9110 §15.5.16 | Only with explicit freshness |
| 416 | Range Not Satisfiable | 4xx Client error | Registered | RFC 9110 §15.5.17 | Only with explicit freshness |
| 417 | Expectation Failed | 4xx Client error | Registered | RFC 9110 §15.5.18 | Only with explicit freshness |
| 418 | (Unused) | 4xx Client error | Reserved, unused | RFC 9110 §15.5.19 | No |
| 421 | Misdirected Request | 4xx Client error | Registered | RFC 9110 §15.5.20 | Only with explicit freshness |
| 422 | Unprocessable Content | 4xx Client error | Registered | RFC 9110 §15.5.21 | Only with explicit freshness |
| 423 | Locked | 4xx Client error | Registered | RFC 4918 §11.3 | Only with explicit freshness |
| 424 | Failed Dependency | 4xx Client error | Registered | RFC 4918 §11.4 | Only with explicit freshness |
| 425 | Too Early | 4xx Client error | Registered | RFC 8470 §5.2 | Only with explicit freshness |
| 426 | Upgrade Required | 4xx Client error | Registered | RFC 9110 §15.5.22 | Only with explicit freshness |
| 428 | Precondition Required | 4xx Client error | Registered | RFC 6585 §3 | No |
| 429 | Too Many Requests | 4xx Client error | Registered | RFC 6585 §4 | No |
| 431 | Request Header Fields Too Large | 4xx Client error | Registered | RFC 6585 §5 | No |
| 451 | Unavailable For Legal Reasons | 4xx Client error | Registered | RFC 7725 §3 | Yes, by default |
| 500 | Internal Server Error | 5xx Server error | Registered | RFC 9110 §15.6.1 | Only with explicit freshness |
| 501 | Not Implemented | 5xx Server error | Registered | RFC 9110 §15.6.2 | Yes, by default |
| 502 | Bad Gateway | 5xx Server error | Registered | RFC 9110 §15.6.3 | Only with explicit freshness |
| 503 | Service Unavailable | 5xx Server error | Registered | RFC 9110 §15.6.4 | Only with explicit freshness |
| 504 | Gateway Timeout | 5xx Server error | Registered | RFC 9110 §15.6.5 | Only with explicit freshness |
| 505 | HTTP Version Not Supported | 5xx Server error | Registered | RFC 9110 §15.6.6 | Only with explicit freshness |
| 506 | Variant Also Negotiates | 5xx Server error | Registered | RFC 2295 §8.1 | Only with explicit freshness |
| 507 | Insufficient Storage | 5xx Server error | Registered | RFC 4918 §11.5 | Only with explicit freshness |
| 508 | Loop Detected | 5xx Server error | Registered | RFC 5842 §7.2 | Only with explicit freshness |
| 510 | Not Extended | 5xx Server error | Obsolete | RFC 2774 §7 | Only with explicit freshness |
| 511 | Network Authentication Required | 5xx Server error | Registered | RFC 6585 §6 | No |
The five status code classes
| Class | Name | Meaning | Registered codes |
|---|---|---|---|
| 1xx | Informational | The request was received and processing continues; an interim response before the final one. | 4 |
| 2xx | Successful | The request was received, understood and accepted. | 10 |
| 3xx | Redirection | The client must take further action, usually following a Location header, to finish the request. | 9 |
| 4xx | Client error | The request has a problem the client can fix: bad syntax, missing credentials, a wrong address. | 29 |
| 5xx | Server error | The server failed to fulfil a request that looks valid. | 11 |
Status codes cacheable by default
| Code | Reason phrase | Defined in |
|---|---|---|
| 200 | OK | RFC 9110 §15.3.1 |
| 203 | Non-Authoritative Information | RFC 9110 §15.3.4 |
| 204 | No Content | RFC 9110 §15.3.5 |
| 206 | Partial Content | RFC 9110 §15.3.7 |
| 300 | Multiple Choices | RFC 9110 §15.4.1 |
| 301 | Moved Permanently | RFC 9110 §15.4.2 |
| 308 | Permanent Redirect | RFC 9110 §15.4.9 |
| 404 | Not Found | RFC 9110 §15.5.5 |
| 405 | Method Not Allowed | RFC 9110 §15.5.6 |
| 410 | Gone | RFC 9110 §15.5.11 |
| 414 | URI Too Long | RFC 9110 §15.5.15 |
| 451 | Unavailable For Legal Reasons | RFC 7725 §3 |
| 501 | Not Implemented | RFC 9110 §15.6.2 |
Reserved, deprecated and obsolete codes
| Code | Reason phrase | Registry status | What it is |
|---|---|---|---|
| 102 | Processing | Obsolete | A WebDAV interim response telling the client that the server has accepted a long-running request and is still working. It was dropped from RFC 4918 and is obsolete. |
| 305 | Use Proxy | Deprecated | Once meant that the resource must be reached through the proxy named in Location. RFC 9110 deprecates it because of security concerns. |
| 306 | (Unused) | Reserved, unused | Reserved. It was used in an earlier HTTP draft ("Switch Proxy") and has no defined meaning now. The number stays reserved so it is not reassigned. |
| 418 | (Unused) | Reserved, unused | Reserved, with no defined behaviour. RFC 9110 keeps the number unassigned so it is not reused. “I’m a teapot” comes from RFC 2324, the April Fools’ Hyper Text Coffee Pot Control Protocol, and is not an HTTP standard. |
| 510 | Not Extended | Obsolete | Once meant that the server needed further extensions to the request (the HTTP Extension Framework). The registry marks it obsolete because the experiment was moved to Historic. |
Codes defined outside RFC 9110
| Code | Reason phrase | Defined in |
|---|---|---|
| 102 | Processing | RFC 2518 §10.1 |
| 103 | Early Hints | RFC 8297 §2 |
| 207 | Multi-Status | RFC 4918 §11.1 |
| 208 | Already Reported | RFC 5842 §7.1 |
| 226 | IM Used | RFC 3229 §10.4.1 |
| 423 | Locked | RFC 4918 §11.3 |
| 424 | Failed Dependency | RFC 4918 §11.4 |
| 425 | Too Early | RFC 8470 §5.2 |
| 428 | Precondition Required | RFC 6585 §3 |
| 429 | Too Many Requests | RFC 6585 §4 |
| 431 | Request Header Fields Too Large | RFC 6585 §5 |
| 451 | Unavailable For Legal Reasons | RFC 7725 §3 |
| 506 | Variant Also Negotiates | RFC 2295 §8.1 |
| 507 | Insufficient Storage | RFC 4918 §11.5 |
| 508 | Loop Detected | RFC 5842 §7.2 |
| 510 | Not Extended | RFC 2774 §7 |
| 511 | Network Authentication Required | RFC 6585 §6 |
How to look up an HTTP status code
- Type a code or a word. Enter a three-digit code such as 404, a class such as 4xx, or a word such as redirect, timeout or teapot. A sentence like “error 502 bad gateway” works too.
- Read the result card. It shows the reason phrase, class, whether the code is current, reserved or obsolete, the RFC section that defines it, whether a cache may reuse it by default, and what it means.
- Check causes and fixes. Use the common causes and fixes to find what to look at first. Treat them as typical suspects, not a diagnosis: your server logs have the real answer.
- Browse the full table. Filter the reference table by text, class or cacheability to compare codes, such as 301 against 308 or 401 against 403.
Frequently asked questions
- Is 418 “I’m a teapot” a real HTTP status code?
- Not as a standard. RFC 9110 §15.5.19 lists 418 as “(Unused)” and reserves the number so it is not assigned to anything else. The teapot joke comes from RFC 2324, the April Fools’ Hyper Text Coffee Pot Control Protocol. Some servers still return it on purpose, but no HTTP specification defines its behaviour.
- What is the difference between 401 and 403?
- 401 Unauthorized means the request lacks valid authentication, so the client can try again with credentials (the response names a scheme in WWW-Authenticate). 403 Forbidden means the server understood who you are, or does not care, and still refuses. Logging in again will not change a 403 unless a different account has permission.
- What is the difference between 301, 302, 307 and 308?
- 301 and 308 are permanent moves; 302 and 307 are temporary. The older 301 and 302 let a client change a POST into a GET when following the redirect, while 307 and 308 require the same method and body. Use 308 or 307 when the method must be kept, and 301 or 302 for ordinary page moves.
- Which status codes are cacheable by default?
- RFC 9110 §15.1 lists 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414 and 501 as heuristically cacheable, and RFC 7725 §3 adds 451, so the registry here marks 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, 451, 501. Any other code is stored by a cache only when the response carries explicit freshness information such as Cache-Control: max-age.
- Why does the table not list 509, 499 or 520?
- They are not in the IANA registry. nginx logs 499 when a client closes the connection and uses 444 to drop one, Cloudflare uses 520 to 527 for errors between it and your origin, and Apache mod_bw uses 509. These are vendor codes: they can help when debugging that product, but other software does not have to understand them. The range 419 to 499 is otherwise unassigned.
- Does the registry include 104 Upload Resumption Supported?
- It has a temporary registration for the resumable upload draft, which expires unless the draft becomes an RFC and the code is made permanent. This page lists only permanent registrations, so 104 is left out. Check the IANA registry for its current state.
- What happened to 413 “Payload Too Large” and 422 “Unprocessable Entity”?
- RFC 9110 renamed them: 413 is now “Content Too Large” and 422 is now “Unprocessable Content”. The numbers and meanings are unchanged, and many servers and libraries still send the old phrases. Clients should rely on the number, not the phrase.
- Do clients have to use the reason phrase?
- No. The phrase is only a human-readable hint, and HTTP/2 and HTTP/3 do not send one at all. Software should act on the three-digit code. A server may send a different phrase than the one in the RFC, and this page shows the registry names.
- What should a client do with a status code it does not know?
- RFC 9110 §15 says to treat it as the x00 code of its class: an unknown 4xx is handled like 400, an unknown 5xx like 500. An unrecognised 1xx is an interim response, so the client keeps waiting for the final one.
How it works
The data is a list of the 63 codes in the IANA HTTP Status Code Registry that are permanently registered, written by hand from RFC 9110 §15 and from the other RFCs the registry cites for the extension codes (RFC 2295, RFC 2518, RFC 2774, RFC 3229, RFC 4918, RFC 5842, RFC 6585, RFC 7725, RFC 8297, RFC 8470). Each entry carries the RFC and section that currently define it. 308 was introduced by RFC 7538 and is now in RFC 9110; 422 was defined by RFC 4918 and moved to RFC 9110; the registry cites the newer document. Reserved numbers (306 and 418) and obsolete or deprecated ones (102, 305, 510) are marked from the registry and RFC 9110. Temporary registrations and vendor codes are not included. Cacheability follows RFC 9110 §15.1 and RFC 9111 §4.2.2: 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, 451, 501 are cacheable by default (the twelve in §15.1 plus 451 from RFC 7725); a few responses (428, 429, 431 and 511, by RFC 6585) must not be stored; and any other final response can be cached only with explicit freshness information. The causes and fixes are typical, from common practice rather than from the RFCs, so they point you where to look first. A lookup treats a three-digit number as a code, “4xx” as a class, one or two digits as a prefix, and anything else as words matched against the phrase, search aliases and meaning. The table filter uses the same matching.
Sources
- IANA: Hypertext Transfer Protocol (HTTP) Status Code Registry
- RFC 9110: HTTP Semantics, §15 Status Codes
- RFC 9110 §15.5.19: 418 (Unused)
- RFC 9111: HTTP Caching, §4.2.2 Calculating Heuristic Freshness
- RFC 6585: Additional HTTP Status Codes (428, 429, 431, 511)
- RFC 7538: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
- RFC 7725: An HTTP Status Code to Report Legal Obstacles (451)
- RFC 8297: An HTTP Status Code for Indicating Hints (103)
- RFC 8470: Using Early Data in HTTP (425)
- RFC 4918: HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
- RFC 5842: Binding Extensions to WebDAV (208, 508)
- RFC 2295: Transparent Content Negotiation in HTTP (506)
- RFC 3229: Delta encoding in HTTP (226)
- RFC 2774: An HTTP Extension Framework (510, historic)
- RFC 2324: Hyper Text Coffee Pot Control Protocol (the 418 teapot joke)
More free tools
- URL ParserSplit a URL into protocol, host (punycode and Unicode), port, path and an editable query table. Strip tracking parameters and resolve relative links.
- JWT DecoderDecode a JWT to its header and payload, read exp, iat and nbf as UTC times, spot expired or alg none tokens, and check HMAC signatures. Runs locally.
- Download Time CalculatorHow long a file takes to download at your speed, or the speed needed to finish in time. Handles bits vs bytes, MB vs MiB and protocol overhead.
- Robots.txt Generator and TesterBuild a robots.txt with per-crawler rules, wildcards and sitemaps, then test any URL path against it as RFC 9309 says a crawler must. Runs in your browser.
- User Agent ParserPaste a User-Agent string to see the browser and version, rendering engine, OS, device type and notable tokens. Explains UA reduction. Runs locally.
- Network Ports ReferenceSearch common TCP and UDP port numbers by number, range or service name: 22 SSH, 443 HTTPS, 3306 MySQL and more, with secure variants and IANA status.
More: Web, URLs, images and networkAll developer toolsAll toolsHome & DIY calculators