Is 418 I am a teapot a real status code?
It is reserved in the IANA registry so that nobody assigns it a serious meaning, but it is not a defined status. Servers that send it are joking or using it informally.
Reserved. Made famous by the 1998 "I'm a teapot" April Fools RFC 2324; not a real status. 418 belongs to the 4xx client error class and is defined in RFC 9110.
Loading the workbench.
Reserved. Made famous by the 1998 "I'm a teapot" April Fools RFC 2324; not a real status. The code is registered with IANA and defined in RFC 9110.
Client error: the request has a problem, so it cannot be fulfilled as sent. Every code from 400 to 499 shares that general meaning, so a client that does not recognise 418 must treat it like 400.
418 began as an April Fools' joke: RFC 2324 (1998) defined the Hyper Text Coffee Pot Control Protocol, where a teapot asked to brew coffee answers I'm a teapot. Developers loved it, and many frameworks and sites still return it as an Easter egg or as a playful way to refuse automated requests. RFC 9110 now lists 418 as reserved and unused, so it can never be given a real meaning that would break that joke.
Do not rely on 418 for real error handling; generic clients treat it as an unspecified 4xx. If a service returns it to block bots, read the body for the actual reason and use an honest User-Agent and a reasonable request rate. Servers that want to reject automated traffic should use a standard code such as 403 or 429, which monitoring tools and client libraries understand.
HTTP/1.1 418 I'm a teapot
Content-Type: text/plain
(reserved in RFC 9110; sent only as a joke)418 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
curl -i.Browse every code on the HTTP status codes page.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
It is reserved in the IANA registry so that nobody assigns it a serious meaning, but it is not a defined status. Servers that send it are joking or using it informally.
A few sites use 418 to refuse automated clients in a light-hearted way. Treat it like a 403 or 429 and check the site's terms and rate limits.
No. 418 is reserved and unused, so a correct server never sends it; a client that receives it should treat it like a generic 4xx response.
No. Caches store a 418 only when Cache-Control or Expires explicitly allows it.
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.