snaptools
chain
#
HTTP 418 I'm a Teapot
⌃⏎ run · ⎋ clear · / focus input
Meaning
send output to
no matches
Result appears here as you type
runs in your browser · nothing uploaded
// about this tool

HTTP 418 I'm a Teapot Online

Updated 2026-07-26

HTTP 418 I'm a Teapot is the internet's best-known joke status code — born from RFC 2324's April Fools' "Hyper Text Coffee Pot Control Protocol" in 1998, and formally reserved (not standard, but not removed either) in RFC 7168. It means exactly what it says: the server is a teapot, and a teapot cannot brew coffee.

Despite being a joke, it's technically valid to send and receive — a handful of real services use it as a deliberate easter egg for requests they want to playfully reject. It's not something to build production error-handling around, but if you've stumbled on this page because a service actually returned it, you've found the internet's favorite piece of HTTP trivia. For every other status code — the real ones — use the full HTTP Status Codes reference.

// how to use

  1. 1 The code is already looked up below — 418 is pre-filled.
  2. 2 Type any other status code to look that one up instead.
  3. 3 Copy the result, or use the full HTTP Status Codes reference for every code at once.

// examples

The code itself
Input
418
Output
418 I'm a Teapot — Client Error (4xx). A joke status code from the April Fools' Hyper Text Coffee Pot Control Protocol.
A real client-error code nearby
Input
400
Output
400 Bad Request — a genuine, RFC-mandated status for malformed requests.

// common uses

Understanding an unexpected 418 response from a third-party API Adding a playful easter egg to a personal or internal API Settling a trivia question about HTTP status codes Checking what a status code in server logs actually means

// faq

Is anything uploaded to a server?
No. The lookup runs entirely in your browser from a built-in table, so nothing you type leaves your machine.
Is 418 a real, usable HTTP status code?
It originated as an April Fools' joke in RFC 2324 (1998), the "Hyper Text Coffee Pot Control Protocol" — a parody spec for controlling coffee pots over HTTP. It was later formally reserved (not removed) in RFC 7168, so it's technically real, just never meant to be serious.
Do any real services actually return 418?
Yes, a handful, mostly as an easter egg — some API frameworks, testing tools, and even Google's own bot-detection systems have used 418 for requests they wanted to playfully reject, since it's memorable and clearly non-standard for real errors.
Should I use 418 in my own API?
Generally no, for anything users depend on — it can confuse client libraries and monitoring tools that don't expect it. It's best reserved for genuine easter eggs, internal jokes, or deliberately playful public APIs where the surprise is the point.
Why does this code specifically mention a teapot?
The joke RFC describes a "coffee pot" that refuses to brew coffee because it is, in fact, a teapot — 418 is the status a teapot returns when asked to perform a coffee pot's job.

// works with your data

Sort & Dedupe Lines Slug Generator Reverse Text Text Repeater Remove Duplicate Lines Whitespace Remover

Use this via API

Get a free API key → 
curl -X POST https://thesnaptools.com/api/v1/tools/http-418 \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"418"}'
Esc
↑↓ navigate ↵ open Esc close