HTTP 418 I’m a teapot

A joke from 1998: a teapot refusing to brew coffee. Some sites use it for fun or to turn away bots.

I’m a teapot

4xx Client errorReservedRFC 9110, section 15.5.19

A joke from 1998: a teapot refusing to brew coffee. Some sites use it for fun or to turn away bots.

Example response
HTTP/1.1 418 I'm a teapot
Content-Type: text/plain
Date: Sun, 15 Nov 2026 09:30:00 GMT

I'm a teapot. I can't brew coffee.

What 418 means

A joke. RFC 2324, published on 1 April 1998, defined the Hyper Text Coffee Pot Control Protocol, where a teapot asked to brew coffee answers “418 I’m a teapot”. It was never part of HTTP itself, but it became so well known that RFC 9110 reserves 418 so it can’t be reused for something serious.

When servers send it

Only when a developer chooses to. Some sites use it as an Easter egg, and some as a light-hearted way to turn away bots or requests they don’t want to handle.

Why you might see it

  • A deliberate Easter egg or bot block.
  • A test endpoint, such as httpbin’s /status/418.

Using it as a developer

  • Don’t use 418 for real errors in an API: clients won’t know what to do with it. Pick the matching 4xx, such as 403 or 429.
  • Many HTTP libraries and frameworks know the name “I’m a teapot” and handle it like any other 4xx.

If you’re visiting a website

  • Nothing to fix. The site is either joking or has decided not to serve your request.

Related codes

  • 403 Forbidden: The server understood who you are and won’t let you do this.
  • 429 Too Many Requests: You’ve sent too many requests in a given time. Slow down and try again later.
  • 400 Bad Request: The server can’t or won’t handle the request because something in it is malformed.

Where it’s defined

418 I’m a teapot is defined in RFC 9110, section 15.5.19, which reserves the number. It’s a 4xx code, the client error class: something is wrong with the request, so sending it again unchanged won’t help.

Other 4xx codes

400 Bad Request · 401 Unauthorized · 402 Payment Required · 403 Forbidden · 404 Not Found · 405 Method Not Allowed · 406 Not Acceptable · 408 Request Timeout · 409 Conflict · 410 Gone · 413 Content Too Large · 414 URI Too Long · 415 Unsupported Media Type · 422 Unprocessable Content · 429 Too Many Requests · 431 Request Header Fields Too Large · 451 Unavailable For Legal Reasons · 499 Client Closed Request

Or search them all in the HTTP status code list.

Questions people ask

What does HTTP 418 I’m a teapot mean?
A joke from 1998: a teapot refusing to brew coffee. Some sites use it for fun or to turn away bots.
Is 418 I’m a teapot a real status code?
Not really. It comes from an April Fools’ RFC. RFC 9110 marks 418 as reserved, to stop it ever being given a serious meaning, because so much software already knows the joke.
Why do some sites return 418?
For fun, or to signal “we won’t serve this” to bots and scrapers without using a code that clients might retry or report as a real error.
↑↓ move↵ openesc close