HTTP 418 I'm a Teapot was defined as an April Fools' joke in RFC 2324 (Hyper Text Coffee Pot Control Protocol). It indicates that the server refuses to brew coffee because it is permanently a teapot. Some servers implement this as an easter egg.
Status
418 I'm a TeapotExample
GET /coffee HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0
Accept: text/htmlHTTP/1.1 418 I'm a Teapot
Content-Type: text/html; charset=utf-8
<!doctype html>
<html>
<body>
<h1>418 I'm a Teapot</h1>
<p>I'm a teapot. I cannot brew coffee.</p>
</body>
</html>How to Troubleshoot
Check if the URL is correct
You may be hitting an easter egg endpoint. Verify you are requesting the correct URL.
Check for bot detection
If you are making automated requests, the server may be using 418 to block bots. Add a proper User-Agent header.
Common Causes
Easter egg or joke response
highThe server intentionally returns 418 as a humorous response, often on specific endpoints.
Anti-bot or anti-scraping measure
mediumSome servers return 418 to bots and scrapers as a non-standard block response.
Related Status Codes
References
| Specification | Section |
|---|---|
| Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) | RFC 2324 §2.3.2 |
Frequently Asked Questions
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.