# Guess the HTTP status: 20 everyday situations

Source: https://checkcraft.ru/en/guides/http-status-game.html · updated 2026-11-20

A game for testers and developers: an everyday situation, pick the HTTP response code. 200, 201, 204, 301, 400, 401, 403, 404, 429, 500, 502, 503, 504 and more.

Practical workflow

Checkcraft is a desktop app for checking APIs and logs without code, with a free edition. [Download, no sign-up →](https://checkcraft.ru/en/download-checkcraft.html#free-download)

A guard will not let you in without a pass: is that 401 or 403? The café moved for good: 301 or 302? Twenty everyday situations, four answers each and a short explanation after every one. The last question has a twist.

Checkcraft · 20 November 2026

Get help with your first test →

## Why a tester should care

The status code is the first thing an automated test sees and the most common thing it checks. But a status only tells you how the server understood the request. It does not tell you whether the result is right: a server can honestly answer 200 and return a wrong total. So after the game, try the practice API where every response is 200 and ten bugs hide inside.

## How to remember the groups

1xx are informational, 2xx mean the request succeeded, 3xx say go elsewhere, 4xx are the asker’s mistake, 5xx are the server’s. 401 means "we do not know who you are", 403 means "we know, but no". 502: a gateway got an invalid answer from the next server; 504: it did not get one in time.

Next step

## Repeat this on your own API

Checkcraft is a desktop app that saves API response checks without code and shows what did not match. Start with a sample, then use your own sanitized data. Free runs on Windows and Linux with no time limit.

[Download Free](https://checkcraft.ru/en/download-checkcraft.html#free-download) · [Download and first run](https://checkcraft.ru/en/download-checkcraft.html)

No sign-up or email needed, the archive is ready in a couple of minutes. See the [edition limits](https://checkcraft.ru/en/pricing.html).

## References

[RFC 9110: HTTP status codes](https://www.rfc-editor.org/rfc/rfc9110#name-status-codes) · [MDN: HTTP response status codes](https://developer.mozilla.org/ru/docs/Web/HTTP/Status)

## Continue with a related task

[Practice API with bugs: find all 10](https://checkcraft.ru/en/guides/api-testing-practice.html) · [HTTP 200 but the result is wrong](https://checkcraft.ru/en/guides/http-200-wrong-result.html) · [401 Unauthorized in an API and Postman: why access is denied](https://checkcraft.ru/en/guides/api-401-error.html) · [403 Forbidden: what it means and how to fix it in an API](https://checkcraft.ru/en/guides/api-403-error.html) · [API error 500: server problem or bad request](https://checkcraft.ru/en/guides/api-500-error.html)

Start with the linked example and compare its result with your own test requirement.

Ask a person

## Get help with your first test

Tell us what you want to test or where you got stuck. We can help you start Checkcraft, choose an example and understand your first run. You can ask before downloading.

[Ask in Telegram](https://t.me/checkcraftchat)Send an email

The Telegram group is public: do not post passwords, tokens or confidential work data. A description of your task is enough to start.

You can also email us support@checkcraft.ru

Page card: /ai/pages/en/guides/http-status-game.md
