Technology · Reference dataset

HTTP Status Codes

Every registered HTTP response status code, with its name, category and technical description, what it means in plain English, an everyday example, who has to fix it (nobody, the browser, the requester or the website), whether trying again can help, how often it is met, whether it is a current standard, and the specification that defines it with a link to the section.

Download options
Look inside

Every record

All 63 records · Last changed November 15, 2026 · Select a column heading to sort. Select a row to read the whole record.

Preview of HTTP Status Codes
Code Name Category Description Plain english Example Who fixes it Try again Seen Status Specification Specification url
100 Continue Informational The client should continue with its request. Go ahead and send the rest of your request. A program asks before uploading a large file, and the server says to go ahead. Nobody Not needed Rarely Standard RFC 9110, Section 15.2.1 https://www.rfc-editor.org/rfc/rfc9110#section-15.2.1
101 Switching Protocols Informational The server is switching protocols. The server agrees to switch to a different way of talking. A chat page upgrades its connection to a WebSocket so that messages arrive instantly. Nobody Not needed Sometimes Standard RFC 9110, Section 15.2.2 https://www.rfc-editor.org/rfc/rfc9110#section-15.2.2
102 Processing Informational The server has received and is processing the request. The server has the request and is still working on it. A file server takes a long time over a big copy and says it has not forgotten you. Nobody Not needed Rarely Standard RFC 2518 https://www.rfc-editor.org/rfc/rfc2518
103 Early Hints Informational Return some response headers before final response. Here is a head start: begin loading these files while the page is prepared. A site tells the browser which fonts and styles to fetch before the page itself arrives. Nobody Not needed Sometimes Standard RFC 8297 https://www.rfc-editor.org/rfc/rfc8297
200 OK Success The request succeeded. It worked. Here is what you asked for. You open a page and it loads. Nobody Not needed Often Standard RFC 9110, Section 15.3.1 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.1
201 Created Success The request succeeded and a resource was created. It worked, and something new was made. You post a comment or create an account. Nobody Not needed Often Standard RFC 9110, Section 15.3.2 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.2
202 Accepted Success The request has been accepted for processing. The request was taken in and will be dealt with later. You ask for a large report and are told it will be emailed when it is ready. Nobody Not needed Sometimes Standard RFC 9110, Section 15.3.3 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.3
203 Non-Authoritative Information Success Returned metadata is from a local or third-party copy. It worked, but a go-between changed the reply on the way. A proxy rewrites part of a page before passing it on to you. Nobody Not needed Rarely Standard RFC 9110, Section 15.3.4 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.4
204 No Content Success There is no content to send for this request. It worked, and there is nothing to send back. You save a setting and the page stays as it is. Nobody Not needed Often Standard RFC 9110, Section 15.3.5 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.5
205 Reset Content Success Tells the client to reset the document that sent this request. It worked. Clear the form you just sent. A data-entry screen empties its boxes, ready for the next record. Nobody Not needed Rarely Standard RFC 9110, Section 15.3.6 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.6
206 Partial Content Success Used when the Range header is sent by the client. Here is the part you asked for, not the whole thing. You skip to the middle of a video, or a download carries on from where it stopped. Nobody Not needed Often Standard RFC 9110, Section 15.3.7 https://www.rfc-editor.org/rfc/rfc9110#section-15.3.7
207 Multi-Status Success Conveys information about multiple resources (WebDAV). Several things were asked for at once, and each has its own result inside. A file-sharing program moves ten files and reports on each one. Nobody Not needed Rarely Standard RFC 4918 https://www.rfc-editor.org/rfc/rfc4918
208 Already Reported Success Members already enumerated (WebDAV). These items were already listed earlier in this reply. A folder that appears twice in a file-server listing is described only once. Nobody Not needed Rarely Standard RFC 5842 https://www.rfc-editor.org/rfc/rfc5842
226 IM Used Success Result of instance-manipulations applied to the resource. Here are only the changes since the copy you already have. A feed reader receives just the new entries, not the whole feed again. Nobody Not needed Rarely Standard RFC 3229 https://www.rfc-editor.org/rfc/rfc3229
300 Multiple Choices Redirection The request has more than one possible response. There is more than one version. Pick one. A document is offered in several formats or languages. The requester After choosing one Rarely Standard RFC 9110, Section 15.4.1 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.1
301 Moved Permanently Redirection The resource has moved permanently. This has a new address for good. Use the new one from now on. A site changes its name and sends old links to the new pages. The browser Automatic Often Standard RFC 9110, Section 15.4.2 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.2
302 Found Redirection The resource has moved temporarily. This is somewhere else for now. Keep using the old address. After signing in, you are sent back to the page you came from. The browser Automatic Often Standard RFC 9110, Section 15.4.3 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.3
303 See Other Redirection Get the requested resource at another URI with a GET. Your request was handled. Fetch the result from this other address. You submit an order form and land on a confirmation page. The browser Automatic Sometimes Standard RFC 9110, Section 15.4.4 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.4
304 Not Modified Redirection The response has not been modified. Nothing has changed. Use the copy you already have. You revisit a page and the browser reuses the images it saved last time. Nobody Not needed Often Standard RFC 9110, Section 15.4.5 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.5
305 Use Proxy Redirection Deprecated. The resource had to be accessed through the proxy given in the Location header. No longer used. It once told the browser to go through a named proxy. You will not meet it: browsers stopped honoring it for security reasons. Nobody No Rarely Deprecated RFC 9110, Section 15.4.6 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.6
306 (Unused) Redirection No longer used. The code is reserved. Reserved and no longer used. It was dropped from an early version of HTTP, and the number is kept empty. Nobody No Rarely Unused RFC 9110, Section 15.4.7 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.7
307 Temporary Redirect Redirection The resource is temporarily at a different URI; method unchanged. This is somewhere else for now. Repeat exactly the same request there. A form you submit is passed to another server without losing what you typed. The browser Automatic Sometimes Standard RFC 9110, Section 15.4.8 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.8
308 Permanent Redirect Redirection The resource is permanently at a different URI; method unchanged. This has moved for good. Repeat exactly the same request at the new address. An API moves to a new address and uploads keep working. The browser Automatic Sometimes Standard RFC 9110, Section 15.4.9 https://www.rfc-editor.org/rfc/rfc9110#section-15.4.9
400 Bad Request Client Error The server cannot process the request due to a client error. The server could not understand the request. A form sends a date that is not a date, or the address contains broken characters. The requester After fixing the request Often Standard RFC 9110, Section 15.5.1 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.1
401 Unauthorized Client Error Authentication is required and has failed or not been provided. You need to sign in, or your sign-in was not accepted. You open your account page after your session has expired. The requester After signing in Often Standard RFC 9110, Section 15.5.2 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.2
402 Payment Required Client Error Reserved for future use. Reserved for a future way to pay. A few services use it to say that payment is needed. An API returns it when a subscription has run out. The requester After fixing the request Rarely Reserved RFC 9110, Section 15.5.3 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.3
403 Forbidden Client Error The client does not have access rights to the content. The server knows who you are and will not let you in. You are signed in as a student and try to open the teacher's gradebook. The requester No Often Standard RFC 9110, Section 15.5.4 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.4
404 Not Found Client Error The server cannot find the requested resource. Nothing is at this address. You mistype a web address, or follow a link to a page that was deleted. The requester After fixing the request Often Standard RFC 9110, Section 15.5.5 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.5
405 Method Not Allowed Client Error The request method is not supported for the resource. The address exists, but not for what you tried to do to it. A program tries to delete a page that can only be read. The requester After fixing the request Sometimes Standard RFC 9110, Section 15.5.6 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.6
406 Not Acceptable Client Error No content matching the acceptance criteria was found. The server has nothing in a format you said you would accept. A program insists on XML and the service only produces JSON. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.7 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.7
407 Proxy Authentication Required Client Error Authentication with the proxy is required. You must sign in to the proxy before it will pass your request on. An office network asks for your login before letting you onto the web. The requester After signing in Rarely Standard RFC 9110, Section 15.5.8 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.8
408 Request Timeout Client Error The server timed out waiting for the request. The server gave up waiting for you to finish sending. A weak phone signal stalls an upload halfway. The requester Yes Sometimes Standard RFC 9110, Section 15.5.9 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.9
409 Conflict Client Error The request conflicts with the current state of the server. The request clashes with what is already there. Two people edit the same document, and the second save is refused. The requester After fixing the request Sometimes Standard RFC 9110, Section 15.5.10 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.10
410 Gone Client Error The requested content has been permanently deleted. This was here once and has been removed for good. A shop takes down the page of a discontinued product on purpose. The requester No Sometimes Standard RFC 9110, Section 15.5.11 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.11
411 Length Required Client Error The Content-Length header is required. The server needs to be told how much data is coming. A program uploads a file without saying how big it is. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.12 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.12
412 Precondition Failed Client Error Preconditions in the request headers were not met. A condition you attached to the request was not true. You say "save only if nobody else has changed it", and somebody had. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.13 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.13
413 Content Too Large Client Error The request body is larger than limits. What you sent is bigger than the server allows. You try to upload a 2 GB video where the limit is 100 MB. The requester After fixing the request Sometimes Standard RFC 9110, Section 15.5.14 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.14
414 URI Too Long Client Error The requested URI is longer than the server will interpret. The address is longer than the server will read. A search form packs thousands of characters into the address. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.15 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.15
415 Unsupported Media Type Client Error The media format is not supported. The server does not accept the kind of file or data you sent. You upload a spreadsheet where only images are allowed. The requester After fixing the request Sometimes Standard RFC 9110, Section 15.5.16 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.16
416 Range Not Satisfiable Client Error The requested range cannot be fulfilled. You asked for a part that does not exist. A download tries to carry on from beyond the end of the file. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.17 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.17
417 Expectation Failed Client Error The Expect request header cannot be met. The server cannot do what the request's Expect header asked. A program asks for a go-ahead before uploading, and the server does not give go-aheads. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.18 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.18
418 I'm a teapot Client Error The server refuses to brew coffee with a teapot. A joke: the server says it is a teapot and cannot brew coffee. An April Fools' Day specification defined it in 1998, and some sites return it for fun. Nobody No Rarely Reserved RFC 9110, Section 15.5.19 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.19
421 Misdirected Request Client Error The request reached a server that cannot produce a response for it. The request reached a server that is not set up to answer for that site. A shared connection is reused for a site the server does not host. The browser Yes Rarely Standard RFC 9110, Section 15.5.20 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.20
422 Unprocessable Content Client Error The request was well formed but had semantic errors. The request was understood, but what it says does not make sense. A booking form sends an end date that comes before its start date. The requester After fixing the request Sometimes Standard RFC 9110, Section 15.5.21 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.21
423 Locked Client Error The resource being accessed is locked (WebDAV). The item is locked and cannot be changed now. A colleague has a shared file open for editing. The requester Later Rarely Standard RFC 4918 https://www.rfc-editor.org/rfc/rfc4918
424 Failed Dependency Client Error The request failed because a request it depended on failed (WebDAV). This step failed because an earlier step it relied on failed. A file cannot be copied because creating its folder failed first. The requester After fixing the request Rarely Standard RFC 4918 https://www.rfc-editor.org/rfc/rfc4918
425 Too Early Client Error The server is unwilling to risk processing a replayed request. The server will not act yet on a request that might be a replayed copy. A request sent in the first instant of a secure connection is asked to wait until the connection is confirmed. The browser Yes Rarely Standard RFC 8470 https://www.rfc-editor.org/rfc/rfc8470
426 Upgrade Required Client Error The client should switch to a different protocol. The server will only answer over a different protocol. A service refuses an old kind of connection and names the one to use. The requester After fixing the request Rarely Standard RFC 9110, Section 15.5.22 https://www.rfc-editor.org/rfc/rfc9110#section-15.5.22
428 Precondition Required Client Error The origin server requires the request to be conditional. The server insists that the request carries a condition. An editor must say which version it is changing, so that two people do not overwrite each other. The requester After fixing the request Rarely Standard RFC 6585 https://www.rfc-editor.org/rfc/rfc6585
429 Too Many Requests Client Error The user has sent too many requests in a given time. You have asked too many times in a short while. Slow down. A program calls a free API a thousand times in a minute. The requester Later Often Standard RFC 6585 https://www.rfc-editor.org/rfc/rfc6585
431 Request Header Fields Too Large Client Error Header fields are too large. The extra information sent with the request is too big. A site's cookies have grown so large that the server rejects every page. The requester After fixing the request Rarely Standard RFC 6585 https://www.rfc-editor.org/rfc/rfc6585
451 Unavailable For Legal Reasons Client Error The resource is unavailable for legal reasons. The server is not allowed to show this for legal reasons. A court orders a page to be blocked in one country. The number is a nod to the novel Fahrenheit 451. Nobody No Rarely Standard RFC 7725 https://www.rfc-editor.org/rfc/rfc7725
500 Internal Server Error Server Error The server encountered an unexpected condition. Something broke on the server, and it cannot say what. A bug in the site's code crashes while building your page. The website Later Often Standard RFC 9110, Section 15.6.1 https://www.rfc-editor.org/rfc/rfc9110#section-15.6.1
501 Not Implemented Server Error The request method is not supported by the server. The server does not know how to do that kind of request. A simple server receives a kind of request it was never built to handle. The website No Rarely Standard RFC 9110, Section 15.6.2 https://www.rfc-editor.org/rfc/rfc9110#section-15.6.2
502 Bad Gateway Server Error The server got an invalid response from an upstream server. A server in the middle got a broken answer from the server behind it. The site's front door is open, but the application behind it has crashed. The website Later Often Standard RFC 9110, Section 15.6.3 https://www.rfc-editor.org/rfc/rfc9110#section-15.6.3
503 Service Unavailable Server Error The server is not ready to handle the request. The server cannot answer right now. It is overloaded or down for maintenance. Ticket sales open and far too many people arrive at once. The website Later Often Standard RFC 9110, Section 15.6.4 https://www.rfc-editor.org/rfc/rfc9110#section-15.6.4
504 Gateway Timeout Server Error The upstream server did not respond in time. A server in the middle waited too long for the server behind it. A report takes so long to build that the front server stops waiting. The website Later Sometimes Standard RFC 9110, Section 15.6.5 https://www.rfc-editor.org/rfc/rfc9110#section-15.6.5
505 HTTP Version Not Supported Server Error The HTTP version is not supported. The server does not support the version of HTTP the request used. A very old program talks to a modern server in a version it has dropped. The requester After fixing the request Rarely Standard RFC 9110, Section 15.6.6 https://www.rfc-editor.org/rfc/rfc9110#section-15.6.6
506 Variant Also Negotiates Server Error Internal configuration error in content negotiation. The server is set up wrongly: its choice between versions loops back on itself. A misconfigured site cannot decide which language version to send. The website No Rarely Standard RFC 2295 https://www.rfc-editor.org/rfc/rfc2295
507 Insufficient Storage Server Error The server cannot store the representation (WebDAV). The server has run out of room to store what you sent. A shared drive is full when you try to save a file. The website Later Rarely Standard RFC 4918 https://www.rfc-editor.org/rfc/rfc4918
508 Loop Detected Server Error An infinite loop was detected (WebDAV). The server found itself going round in circles and stopped. Folders on a file server link to each other in a loop. The website No Rarely Standard RFC 5842 https://www.rfc-editor.org/rfc/rfc5842
510 Not Extended Server Error Further extensions are required to fulfill the request. Obsolete. The server wanted the request to use an extension that was never widely adopted. You will not meet it: the experiment it belonged to was retired. Nobody No Rarely Obsolete RFC 2774 https://www.rfc-editor.org/rfc/rfc2774
511 Network Authentication Required Server Error The client needs to authenticate to gain network access. You must sign in to the network before you can reach the web. Hotel or airport Wi-Fi shows its login page first. The requester After signing in Sometimes Standard RFC 6585 https://www.rfc-editor.org/rfc/rfc6585

Open this data in a free tool: CSV to JSON · JSON formatter · SQL INSERT generator · CSV to XML

CSV / JSON / XML

Put this data to work.

All 63 records are available without a pass, within the free request limits.

  • CSV for spreadsheets and lookup tables
  • JSON for apps and data analysis
  • XML for imports and integrations
Choose your file

Your key is used for this request and is not saved by this page.

Commercial use is allowed, free or paid.

Downloaded a CSV? Convert CSV to JSON, generate SQL inserts, remove duplicate lines, or sort a list with the free tools.

Scope and sources

Last checked against sources: October 15, 2026.

Last changed: November 15, 2026. This is when we last changed the data or its description. It doesn’t mean the data runs up to that date.

HTTP Status Codes has 63 records and 12 fields: Code, Name, Category, Description, Plain english, Example, Who fixes it, Try again, Seen, Status, Specification, Specification url.

A complete download includes all 63 records currently held in this dataset. Check the description and sources to decide whether its scope fits your project.

Use this dataset through the API
GET https://mysafeinfo.com/api/data/httpstatuscodes

Choose a format, sort, or request fewer rows. A pass key gives access to the complete dataset. See the examples and parameters.

More in Technology

Git Commands HTML Colors Microsoft Access Data Types MySQL Data Types Operating Systems Programming Languages

Download a category with your pass