Skip to main content
ponderloop

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

Try 404, 4xx, redirect, timeout or teapot

404 Not Found

404 Not Found

Class
4xx Client error
Registry status
Registered
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.

Registered HTTP status codes with class, registry status, defining RFC section and default cacheability
CodeReason phraseClassRegistry statusDefined inCacheable by default?
100Continue1xx InformationalRegisteredRFC 9110 §15.2.1No
101Switching Protocols1xx InformationalRegisteredRFC 9110 §15.2.2No
102Processing1xx InformationalObsoleteRFC 2518 §10.1No
103Early Hints1xx InformationalRegisteredRFC 8297 §2No
200OK2xx SuccessfulRegisteredRFC 9110 §15.3.1Yes, by default
201Created2xx SuccessfulRegisteredRFC 9110 §15.3.2Only with explicit freshness
202Accepted2xx SuccessfulRegisteredRFC 9110 §15.3.3Only with explicit freshness
203Non-Authoritative Information2xx SuccessfulRegisteredRFC 9110 §15.3.4Yes, by default
204No Content2xx SuccessfulRegisteredRFC 9110 §15.3.5Yes, by default
205Reset Content2xx SuccessfulRegisteredRFC 9110 §15.3.6Only with explicit freshness
206Partial Content2xx SuccessfulRegisteredRFC 9110 §15.3.7Yes, by default
207Multi-Status2xx SuccessfulRegisteredRFC 4918 §11.1Only with explicit freshness
208Already Reported2xx SuccessfulRegisteredRFC 5842 §7.1Only with explicit freshness
226IM Used2xx SuccessfulRegisteredRFC 3229 §10.4.1Only with explicit freshness
300Multiple Choices3xx RedirectionRegisteredRFC 9110 §15.4.1Yes, by default
301Moved Permanently3xx RedirectionRegisteredRFC 9110 §15.4.2Yes, by default
302Found3xx RedirectionRegisteredRFC 9110 §15.4.3Only with explicit freshness
303See Other3xx RedirectionRegisteredRFC 9110 §15.4.4Only with explicit freshness
304Not Modified3xx RedirectionRegisteredRFC 9110 §15.4.5No
305Use Proxy3xx RedirectionDeprecatedRFC 9110 §15.4.6Only with explicit freshness
306(Unused)3xx RedirectionReserved, unusedRFC 9110 §15.4.7No
307Temporary Redirect3xx RedirectionRegisteredRFC 9110 §15.4.8Only with explicit freshness
308Permanent Redirect3xx RedirectionRegisteredRFC 9110 §15.4.9Yes, by default
400Bad Request4xx Client errorRegisteredRFC 9110 §15.5.1Only with explicit freshness
401Unauthorized4xx Client errorRegisteredRFC 9110 §15.5.2Only with explicit freshness
402Payment Required4xx Client errorRegisteredRFC 9110 §15.5.3Only with explicit freshness
403Forbidden4xx Client errorRegisteredRFC 9110 §15.5.4Only with explicit freshness
404Not Found4xx Client errorRegisteredRFC 9110 §15.5.5Yes, by default
405Method Not Allowed4xx Client errorRegisteredRFC 9110 §15.5.6Yes, by default
406Not Acceptable4xx Client errorRegisteredRFC 9110 §15.5.7Only with explicit freshness
407Proxy Authentication Required4xx Client errorRegisteredRFC 9110 §15.5.8Only with explicit freshness
408Request Timeout4xx Client errorRegisteredRFC 9110 §15.5.9Only with explicit freshness
409Conflict4xx Client errorRegisteredRFC 9110 §15.5.10Only with explicit freshness
410Gone4xx Client errorRegisteredRFC 9110 §15.5.11Yes, by default
411Length Required4xx Client errorRegisteredRFC 9110 §15.5.12Only with explicit freshness
412Precondition Failed4xx Client errorRegisteredRFC 9110 §15.5.13Only with explicit freshness
413Content Too Large4xx Client errorRegisteredRFC 9110 §15.5.14Only with explicit freshness
414URI Too Long4xx Client errorRegisteredRFC 9110 §15.5.15Yes, by default
415Unsupported Media Type4xx Client errorRegisteredRFC 9110 §15.5.16Only with explicit freshness
416Range Not Satisfiable4xx Client errorRegisteredRFC 9110 §15.5.17Only with explicit freshness
417Expectation Failed4xx Client errorRegisteredRFC 9110 §15.5.18Only with explicit freshness
418(Unused)4xx Client errorReserved, unusedRFC 9110 §15.5.19No
421Misdirected Request4xx Client errorRegisteredRFC 9110 §15.5.20Only with explicit freshness
422Unprocessable Content4xx Client errorRegisteredRFC 9110 §15.5.21Only with explicit freshness
423Locked4xx Client errorRegisteredRFC 4918 §11.3Only with explicit freshness
424Failed Dependency4xx Client errorRegisteredRFC 4918 §11.4Only with explicit freshness
425Too Early4xx Client errorRegisteredRFC 8470 §5.2Only with explicit freshness
426Upgrade Required4xx Client errorRegisteredRFC 9110 §15.5.22Only with explicit freshness
428Precondition Required4xx Client errorRegisteredRFC 6585 §3No
429Too Many Requests4xx Client errorRegisteredRFC 6585 §4No
431Request Header Fields Too Large4xx Client errorRegisteredRFC 6585 §5No
451Unavailable For Legal Reasons4xx Client errorRegisteredRFC 7725 §3Yes, by default
500Internal Server Error5xx Server errorRegisteredRFC 9110 §15.6.1Only with explicit freshness
501Not Implemented5xx Server errorRegisteredRFC 9110 §15.6.2Yes, by default
502Bad Gateway5xx Server errorRegisteredRFC 9110 §15.6.3Only with explicit freshness
503Service Unavailable5xx Server errorRegisteredRFC 9110 §15.6.4Only with explicit freshness
504Gateway Timeout5xx Server errorRegisteredRFC 9110 §15.6.5Only with explicit freshness
505HTTP Version Not Supported5xx Server errorRegisteredRFC 9110 §15.6.6Only with explicit freshness
506Variant Also Negotiates5xx Server errorRegisteredRFC 2295 §8.1Only with explicit freshness
507Insufficient Storage5xx Server errorRegisteredRFC 4918 §11.5Only with explicit freshness
508Loop Detected5xx Server errorRegisteredRFC 5842 §7.2Only with explicit freshness
510Not Extended5xx Server errorObsoleteRFC 2774 §7Only with explicit freshness
511Network Authentication Required5xx Server errorRegisteredRFC 6585 §6No

The five status code classes

The first digit gives the class (RFC 9110 §15). A client that does not know a code must treat it like the x00 code of its class.
ClassNameMeaningRegistered codes
1xxInformationalThe request was received and processing continues; an interim response before the final one.4
2xxSuccessfulThe request was received, understood and accepted.10
3xxRedirectionThe client must take further action, usually following a Location header, to finish the request.9
4xxClient errorThe request has a problem the client can fix: bad syntax, missing credentials, a wrong address.29
5xxServer errorThe server failed to fulfil a request that looks valid.11

Status codes cacheable by default

A cache may reuse these without explicit freshness headers: 13 codes. RFC 9110 §15.1 lists 12 of them; 451 is added by RFC 7725 §3. Any other code is cached only when the response says how long it stays fresh. In RFC 9111 this is called heuristically cacheable, formerly “cacheable by default”.
CodeReason phraseDefined in
200OKRFC 9110 §15.3.1
203Non-Authoritative InformationRFC 9110 §15.3.4
204No ContentRFC 9110 §15.3.5
206Partial ContentRFC 9110 §15.3.7
300Multiple ChoicesRFC 9110 §15.4.1
301Moved PermanentlyRFC 9110 §15.4.2
308Permanent RedirectRFC 9110 §15.4.9
404Not FoundRFC 9110 §15.5.5
405Method Not AllowedRFC 9110 §15.5.6
410GoneRFC 9110 §15.5.11
414URI Too LongRFC 9110 §15.5.15
451Unavailable For Legal ReasonsRFC 7725 §3
501Not ImplementedRFC 9110 §15.6.2

Reserved, deprecated and obsolete codes

These numbers are in the registry but should not be used as live status codes.
CodeReason phraseRegistry statusWhat it is
102ProcessingObsoleteA 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.
305Use ProxyDeprecatedOnce meant that the resource must be reached through the proxy named in Location. RFC 9110 deprecates it because of security concerns.
306(Unused)Reserved, unusedReserved. 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, unusedReserved, 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.
510Not ExtendedObsoleteOnce 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

17 registered codes come from other documents: RFC 2295, RFC 2518, RFC 2774, RFC 3229, RFC 4918, RFC 5842, RFC 6585, RFC 7725, RFC 8297, RFC 8470. The registry cites the document that defines each code today.
CodeReason phraseDefined in
102ProcessingRFC 2518 §10.1
103Early HintsRFC 8297 §2
207Multi-StatusRFC 4918 §11.1
208Already ReportedRFC 5842 §7.1
226IM UsedRFC 3229 §10.4.1
423LockedRFC 4918 §11.3
424Failed DependencyRFC 4918 §11.4
425Too EarlyRFC 8470 §5.2
428Precondition RequiredRFC 6585 §3
429Too Many RequestsRFC 6585 §4
431Request Header Fields Too LargeRFC 6585 §5
451Unavailable For Legal ReasonsRFC 7725 §3
506Variant Also NegotiatesRFC 2295 §8.1
507Insufficient StorageRFC 4918 §11.5
508Loop DetectedRFC 5842 §7.2
510Not ExtendedRFC 2774 §7
511Network Authentication RequiredRFC 6585 §6

How to look up an HTTP status code

  1. 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.
  2. 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.
  3. 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.
  4. 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

More: Web, URLs, images and networkAll developer toolsAll toolsHome & DIY calculators