Skip to main content

HTTP Status Codes

Search every HTTP status code by number, name or meaning, with its defining RFC, whether it is cacheable and its registry state.

Status codes

Class

1xx · Informational4 codes

2xx · Success10 codes

3xx · Redirection9 codes

4xx · Client error29 codes

5xx · Server error11 codes

200 OK

Code
200
Class
2xx

200 OK · Success

The request succeeded and the body holds the result.

Details

Defined inRFC 9110 §15.3.1
Cacheable by defaultYes
RegistryStandard

Every code

Codes that match the search are drawn in ink; the chosen one is ringed.

Runs in your browser; nothing you enter leaves this page.

How it works

Searching the list

Type a number, a name such as Not Found, or a few words of the meaning, and the list narrows as you type. The class buttons keep only 1xx informational, 2xx success, 3xx redirection, 4xx client error or 5xx server error codes.

Pressing a code opens its details: a plain-language meaning, the RFC and section that define it, and a link to that section.

What the details mean

Cacheable by default marks the codes a cache may store without explicit freshness headers, following RFC 9110 section 15.1. Any code can still be made cacheable or not with Cache-Control.

Registry says whether the code is standard, deprecated, or unused (a number the IANA registry reserves but nobody should send). The chart at the foot draws every code; the ones matching your search are filled in ink.

More tools

All 238 tools