QTNest logoQTNest

Which HTTP Status Code Are You?

200 OK, 404 Not Found, 418 Teapot or 500 Internal Server Error? 8 questions to find your status code.

Question 1 of 80%

Someone asks you for something you cannot give. You:

Frequently Asked Questions

How does the quiz choose my status code?

Each answer adds a point toward one of the eight codes. After eight questions, the code with the most points is your match.

Which status codes can I get?

200 OK, 201 Created, 301 Moved Permanently, 403 Forbidden, 404 Not Found, 418 I'm a Teapot, 429 Too Many Requests or 500 Internal Server Error.

Do I need to know anything about HTTP?

No. Every question is about your personality rather than the protocol, so anyone can take it — though developers will enjoy the references more.

Is 418 a real status code?

418 I'm a Teapot comes from a 1998 April Fools RFC for the Hyper Text Coffee Pot Control Protocol. It is not a real HTTP code, but it has been kept alive by popular demand and is implemented as a joke in many frameworks.

Is my data collected?

No. Everything runs in your browser and no answers or results are stored or sent anywhere.

Which HTTP Status Code Are You? — From 200 OK to 418 Teapot

Every developer has a favourite status code, and most of them say something unflattering about the person who picked it. 200 OK is the quiet reliability nobody writes blog posts about. 201 Created leaves something behind every time. 301 Moved Permanently outgrew where it was and told everyone properly. 403 Forbidden knows exactly who you are and is still saying no. 404 Not Found is somehow the most famous one despite being defined by absence. 418 I'm a Teapot started as an April Fools joke in 1998 and the internet refused to let it die. 429 Too Many Requests knows its limits and enforces them politely. And 500 Internal Server Error is pure chaos with no stack trace.

This quiz matches your temperament to one of the eight. The questions are about how you handle being asked for something you cannot give, what happens when people ask too much of you, your relationship with rules, and the legacy you would pick — not about memorising the RFC.

Each answer adds a point to one code, and the highest total at the end is your result. You will get your status code, a short read on what it says about you, and three traits that fit.

It runs entirely in your browser with nothing stored, and the result is built to share. Post yours in the dev channel and find out who the 500s are.

How to Use the Which HTTP Status Code Are You?

  1. Read each of the eight questions and pick the answer that feels most like you.
  2. No HTTP knowledge required — every question is about personality.
  3. Your status code appears the moment you answer the last question.
  4. Read your code description and the three traits behind it.
  5. Tap "Share result" to compare with other developers, or "Play again" for a different run.

Related Tools