HTTP status codes, in plain words.
Every answer a website gives has a three-digit code. These are the ones you'll actually meet, what they mean, and what to do about them.
Success
- 200 OKThe request worked and the page came back. This is what a healthy site answers.
- 201 CreatedThe request made something new, for example an API call that added a record.
- 204 No ContentThe request worked and there was nothing to send back.
Redirects
- 301 Moved PermanentlyThe address has moved for good; the response says where. Browsers follow it automatically.
- 302 FoundA temporary redirect: go to this other address for now.
- 304 Not ModifiedNothing changed since the browser last asked, so it should use its cached copy.
- 307 Temporary RedirectLike 302, but the browser must repeat the request exactly (same method and body) at the new address.
- 308 Permanent RedirectLike 301, but the browser must repeat the request exactly at the new address.
Client errors: the request was the problem
- 400 Bad RequestThe server couldn't understand the request.
- 401 UnauthorizedThe page needs a sign-in (or an API key) and none was given.
- 403 ForbiddenThe server understood the request but refuses it.
- 404 Not FoundThere's nothing at this address.
- 405 Method Not AllowedThe address exists, but not for this kind of request (for example POST to a page that only accepts GET).
- 408 Request TimeoutThe server gave up waiting for the request to arrive.
- 410 GoneThe page used to exist and was removed on purpose.
- 422 Unprocessable ContentThe request was well-formed, but its contents don't make sense (a form with invalid values).
- 429 Too Many RequestsThe server is rate-limiting: too many requests from this client in a short time.
Server errors: the site was the problem
- 500 Internal Server ErrorThe application crashed while handling the request.
- 501 Not ImplementedThe server doesn't support what was asked (usually the request method).
- 502 Bad GatewayA proxy or load balancer in front of the site got an invalid answer (or none) from the application behind it.
- 503 Service UnavailableThe server is up but can't serve right now: overloaded, or in maintenance.
- 504 Gateway TimeoutThe proxy waited for the application and it didn't answer in time.
- 507 Insufficient StorageThe server has run out of space to store what the request needed.
- 520 Web Server Returned an Unknown Error (Cloudflare)Cloudflare got an answer from your server that it couldn't understand.
- 521 Web Server Is Down (Cloudflare)Cloudflare couldn't connect to your origin server at all.
- 522 Connection Timed Out (Cloudflare)Cloudflare reached out to your origin and got no answer in time.
- 524 A Timeout Occurred (Cloudflare)The connection to the origin worked, but it took more than 100 seconds to answer.
Quick checks, no sign-up.
Is it down right now?
Check whether a website is down for everyone or just for you.
SSL certificate checker
See when a site's certificate expires, who issued it, and whether browsers trust it.
Domain expiry checker
Find out when a domain name's registration runs out, before it does.
Website speed test
Where the time goes when a page is requested: DNS, connection, TLS, server, download.
Cron job tester
Make a test URL, have your cron job call it, and watch the call arrive.
Uptime and SLA calculator
What 99.9% really means: the downtime an uptime percentage allows per day, month and year.
Status page example
See what a public status page looks like, with your company's name on it.
Next time, be the first to know.
Let someone else watch the shop. If anything breaks, you will hear it from us, not from a customer.