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.

2xx Success

The request was received, understood, and accepted.

3xx Redirection

The client needs to take additional action to complete the request.

4xx Client Error

The request contains bad syntax or cannot be fulfilled.

400

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.

401

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.

403

Forbidden

The server understood the request and won't allow it. Unlike 401, sending the same credentials again won't help.

404

Not Found

The server can't find anything at this URL. The path is wrong, the resource was removed, or it was never there.

405

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.

408

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.

409

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.

410

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."

413

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.

415

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.

422

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.

429

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.

500

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.

502

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.

503

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.

504

Gateway Timeout

A proxy or load balancer forwarded your request and gave up waiting for the server behind it to answer.

520

Web Server Error

Cloudflare-specific. Cloudflare connected to your origin server and got a response it couldn't use, or no response at all.

521

Web Server Down

Cloudflare-specific. Cloudflare tried to connect to your origin server and the connection was refused.

522

Connection Timed Out

Cloudflare-specific. Cloudflare tried to connect to your origin and the connection timed out.

523

Origin Unreachable

Cloudflare-specific. Cloudflare can't find a network route to your origin server.

525

SSL Handshake Failed

Cloudflare-specific. Cloudflare connected to your origin but couldn't complete the TLS handshake with it.

530

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