RelicRELIC

HTTP Status Codes

A searchable reference for every common HTTP status code, with what each one means. Search by number or by name.

Runs entirely in your browser. Nothing you type is uploaded.
1xx Informational
100
Continue
The server got the request headers and the client should send the body.
101
Switching Protocols
The server agrees to switch protocols, often to WebSocket.
2xx Success
200
OK
The request succeeded. The standard response for a healthy GET.
201
Created
The request succeeded and a new resource was created.
202
Accepted
The request was accepted for processing, but it is not done yet.
204
No Content
Success, but there is no body to return. Common for DELETE.
206
Partial Content
The server is returning part of the resource, as a range request asked.
3xx Redirection
301
Moved Permanently
The resource has a new permanent URL. Update your links.
302
Found
The resource is temporarily at a different URL.
304
Not Modified
The cached copy is still fresh, so nothing new is sent.
307
Temporary Redirect
Like 302, but the method must not change on the redirect.
308
Permanent Redirect
Like 301, but the method must not change on the redirect.
4xx Client Error
400
Bad Request
The server could not understand the request, often malformed input.
401
Unauthorized
Authentication is required or has failed. Really means unauthenticated.
402
Payment Required
Reserved for future use, sometimes used for paywalls and quotas.
403
Forbidden
The server understood but refuses to authorize it. You lack permission.
404
Not Found
The server cannot find the requested resource. The classic one.
405
Method Not Allowed
The HTTP method is not supported for this resource.
406
Not Acceptable
The server cannot produce a response matching the Accept headers.
408
Request Timeout
The client took too long to send the request.
409
Conflict
The request conflicts with the current state, like a version clash.
410
Gone
The resource was here but is permanently gone, with no forwarding address.
411
Length Required
The server needs a Content-Length header and did not get one.
413
Payload Too Large
The request body is bigger than the server is willing to process.
414
URI Too Long
The requested URL is longer than the server will interpret.
415
Unsupported Media Type
The body format is not one the server can handle.
418
I'm a Teapot
An April Fools joke from 1998. A teapot cannot brew coffee.
422
Unprocessable Content
The syntax is fine but the content failed validation.
425
Too Early
The server will not risk processing a request that might be replayed.
429
Too Many Requests
You have been rate limited. Slow down and try again later.
431
Request Header Fields Too Large
The headers are too large for the server to process.
451
Unavailable For Legal Reasons
The resource is blocked for legal reasons, like a takedown.
5xx Server Error
500
Internal Server Error
Something broke on the server with no more specific message.
501
Not Implemented
The server does not support the functionality to fulfill the request.
502
Bad Gateway
A gateway or proxy got an invalid response from the upstream server.
503
Service Unavailable
The server is overloaded or down for maintenance. Try again soon.
504
Gateway Timeout
A gateway or proxy did not get a response from upstream in time.
505
HTTP Version Not Supported
The server does not support the HTTP version in the request.
507
Insufficient Storage
The server cannot store what it needs to complete the request.
511
Network Authentication Required
You need to authenticate to get network access, like a captive portal.

Know what the server is telling you

Every HTTP response carries a status code, and the number is a quick summary of what happened. The 1xx range is informational, 2xx means success, 3xx is a redirect, 4xx blames the request, and 5xx blames the server. Search this reference by the number or by a word like “timeout” or “forbidden” to find the one you need, read its one-line meaning, and copy the code in a click. It is a handy thing to keep open while you are debugging an API.

For the responses you keep pasting into tickets

The failing request, the headers you grabbed, the curl command that reproduces it. Debugging is mostly copying things, and then losing them the moment you close the tab. Relic is an encrypted, searchable memory for everything you copy. It auto-tags URLs, JSON, and code on your device, keeps them forever, and syncs across machines, all end-to-end encrypted and open source. Look codes up here for free, and keep the debugging trail for good.

Frequently asked questions

What does HTTP status 403 mean?

403 Forbidden means the server understood your request but refuses to authorize it, so you simply lack permission for that resource. It is different from 401 Unauthorized, which really means unauthenticated: 401 says the server does not know who you are, while 403 says it knows and still says no. This searchable reference lists 403 alongside every other common code with a one-line meaning.

What do the status code classes 1xx to 5xx mean?

The first digit sorts every response into a class: 1xx is informational, 2xx is success, 3xx is a redirect, 4xx blames the request (a client error), and 5xx blames the server. Knowing just the class tells you which side to start debugging on before you even read the specific number. This tool groups its list under those five headings.

How do I look up a status code here?

Type into the search box and the list filters live. You can search by the number (like 404), by the name (like "timeout" or "forbidden"), or by any word in the description, and matching rows are grouped by their class. Each row has a Copy button so you can grab the number in a click.

What is the difference between 301 and 302 redirects?

301 Moved Permanently says the resource has a new permanent URL and you should update your links, while 302 Found says it is only temporarily at a different URL. There are also 307 and 308, which behave like 302 and 301 respectively but guarantee the HTTP method will not change on the redirect. All four are in the 3xx section of this reference.

Is 418 I'm a Teapot a real status code?

It is real in the sense that it is a registered code, but it started as an April Fools joke from 1998: a teapot politely refusing to brew coffee. You will not see it in normal APIs, though some servers use it playfully. It is included here in the 4xx list because people genuinely do look it up.

More free tools
JSON Formatter
json formatter
Base64 Encode / Decode
base64 decode
Diff Checker
diff checker
URL Encode / Decode
url decoder
UUID Generator
uuid generator
Epoch Converter
epoch converter
All tools