Free Tools
HTTP status codes
Every status code explained in plain language. Not the RFC definition. What it actually means when you see it in the wild.
1xx Informational
The server received the request and is continuing the process.
Continue
The server received the request headers. The client should proceed to send the body. Used with large uploads to check if the server will accept the request before sending the full payload.
Switching Protocols
The server is switching to the protocol the client requested. Most commonly seen when upgrading an HTTP connection to a WebSocket.
Processing
The server received the request and is still working on it. Prevents the client from timing out on long-running operations.
Early Hints
The server is sending headers before the final response. Lets the browser start loading CSS and JS while the server is still generating the page.
2xx Success
The request was received, understood, and accepted.
OK
The request succeeded. This is the response you want to see. For GET requests, the body contains the requested resource. For POST requests, the body contains the result of the action.
Created
The request succeeded and a new resource was created. Typically returned by POST endpoints. The Location header usually points to the new resource.
Accepted
The request was accepted but hasn't been processed yet. Used for async operations: the server is saying "I got it, I'll handle it later." Common with job queues and webhooks.
No Content
The request succeeded but there's nothing to send back. Common for DELETE requests and PUT/PATCH updates where you don't need the updated resource returned.
Partial Content
The server is delivering only part of the resource. Used for range requests: downloading a large file in chunks, or resuming a broken download.
3xx Redirection
The client needs to take additional action to complete the request.
Moved Permanently
The resource has permanently moved to a new URL. Search engines transfer ranking to the new URL. Browsers cache this aggressively: if you set one by mistake, it can be hard to undo.
Found
The resource is temporarily at a different URL. The client should continue using the original URL for future requests. Often used for login redirects and temporary maintenance pages.
See Other
The response to your request is at a different URL, and you should use GET to retrieve it. Common after a POST: the server is saying "the thing you created is over here."
Not Modified
The resource hasn't changed since your last request. The server is telling the client to use its cached copy. This is a good thing: it means caching is working.
Temporary Redirect
Like 302 but stricter: the client must use the same HTTP method for the redirected request. A POST stays a POST. 302 technically allows the method to change.
Permanent Redirect
Like 301 but stricter: the client must use the same HTTP method. A POST to the old URL should POST to the new URL too.
4xx Client Error
The request contains bad syntax or cannot be fulfilled.
Bad Request
The server can't process the request because something is wrong with it. Missing required fields, invalid JSON, wrong data types. Check your request body and query parameters.
Unauthorized
The server needs to know who you are, and the request either didn't say or said it wrong. Despite the name, 401 is about authentication (who you are), not authorization (what you're allowed to do). That's 403.
Forbidden
The server understood the request and won't allow it. Unlike 401, sending the same credentials again won't help.
Not Found
The server can't find anything at this URL. The path is wrong, the resource was removed, or it was never there.
Method Not Allowed
The HTTP method isn't supported for this URL. You sent a DELETE to an endpoint that only accepts GET and POST. The response includes an Allow header listing valid methods.
Request Timeout
The server gave up waiting for the client to finish sending its request. It's the server saying the client was too slow, not the other way around.
Conflict
The request conflicts with the current state of the resource. Common with concurrent updates: two people editing the same record, or trying to create a resource that already exists.
Gone
The resource existed but has been permanently deleted. Unlike 404, this is deliberate: the server is saying "it was here, it's not anymore, and it's not coming back."
Content Too Large
The request body is larger than the server is willing to accept. Common when uploading files that exceed the server's size limit.
Unsupported Media Type
The server doesn't support the Content-Type of the request. You sent XML but the endpoint only accepts JSON, or you forgot the Content-Type header entirely.
Unprocessable Content
The request is well-formed but the content is invalid. The JSON is valid, but the data doesn't pass validation: missing required fields, values out of range, business rule violations.
Too Many Requests
The client sent too many requests in a given amount of time, and the server is asking it to slow down.
5xx Server Error
The server failed to fulfill a valid request.
Internal Server Error
Something went wrong on the server and it has nothing more specific to say. It's what most frameworks return when your code throws an exception it doesn't handle.
Bad Gateway
A server in the middle, like a load balancer, reverse proxy or CDN, tried to pass your request on to the server behind it and got back something it couldn't use. Either the upstream server didn't answer properly, or the connection closed before a full response came back.
Service Unavailable
The server is up but can't handle the request right now. It's meant to be temporary: overload, maintenance, or an app that isn't ready yet.
Gateway Timeout
A proxy or load balancer forwarded your request and gave up waiting for the server behind it to answer.
Web Server Error
Cloudflare-specific. Cloudflare connected to your origin server and got a response it couldn't use, or no response at all.
Web Server Down
Cloudflare-specific. Cloudflare tried to connect to your origin server and the connection was refused.
Connection Timed Out
Cloudflare-specific. Cloudflare tried to connect to your origin and the connection timed out.
Origin Unreachable
Cloudflare-specific. Cloudflare can't find a network route to your origin server.
SSL Handshake Failed
Cloudflare-specific. Cloudflare connected to your origin but couldn't complete the TLS handshake with it.
Origin DNS Error or Tunnel Error
Cloudflare-specific. Cloudflare couldn't find where to send the request: it couldn't resolve the origin's hostname, or the Cloudflare Tunnel for it isn't connected.
Get alerted when your endpoints return unexpected status codes.
Larm checks your HTTP endpoints and alerts you when they return status codes outside your expected range. Multi-location verification, full request traces.
Sign Up Free