404 Checker
HTTP Status Codes
10 Codes Documented
2XX — Successful
Indicates that the client's request was successfully received, understood, accepted, and processed by the server.
HTTP
200
OK
RFC 9110
The request has succeeded. The requested resource is available and has been fetched and transmitted in the message body. This is the standard, most common HTTP status code for successful webpage, image, and API requests.
HTTP
201
Created
RFC 9110
The request has been fulfilled and has resulted in one or more new resources being created on the server. Commonly issued following POST or PUT requests, typically accompanied by a Location header referencing the newly created resource URI.
HTTP
202
Accepted
RFC 9110
The client request has been accepted for processing, but processing has not completed. The request might or might not eventually be acted upon, as it is non-committal. Commonly used for asynchronous or batch job processing.
HTTP
203
Non-Authoritative Information
RFC 9110
Indicates that the request was successful, but the returned payload was modified or transformed by an intermediate proxy or gateway from that of the origin server's 200 (OK) response.
HTTP
204
No Content
RFC 9110
The request has been successfully processed, but there is no additional content to send in the response payload. Browsers receiving a 204 status do not change their active document view. This status code should never include a message body.
HTTP
205
Reset Content
RFC 9110
The request has been successful and the server directs the user agent to reset the document view that caused the request to be sent (for example, clearing an HTML form so the user can easily enter fresh data). Must not include a message body.
HTTP
206
Partial Content
RFC 9110
The server is delivering only part of the resource due to a Range header sent by the client. Widely used for HTTP video/audio streaming seek bars, resumable file downloads, and split multi-threaded download managers.
HTTP
207
Multi-Status
RFC 4918
A WebDAV XML status response containing multiple independent status codes for sub-operations on multiple resources.
HTTP
208
Already Reported
RFC 5842
Used inside a WebDAV DAV:propstat response element to avoid repeatedly enumerating the internal members of collection bindings that were already reported.
HTTP
226
IM Used
RFC 3229
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations (delta encodings) applied to the current instance.
Verify Status Codes in Real-Time
Encountered an unexpected HTTP response on your website? Use our free tool to inspect the full header and status chain.
Launch 404 Checker