HTTP 418 I'm a Teapot — Easter Egg Status Code

Overview

HTTP 418 I'm a Teapot was defined as an April Fools joke in the Hyper Text Coffee Pot Control Protocol (HTCPCP) and is used as an Easter egg.

Key Details

• Defined in RFC 2324 (1998 April Fools) for the HTCPCP protocol
• The teapot refuses to brew coffee because it is a teapot
• Not part of the actual HTTP specification but widely implemented as an Easter egg
• Google, major websites, and frameworks include 418 responses
• Some APIs use 418 to indicate 'this endpoint is intentionally disabled'

Common Causes

• Website or API intentionally returning 418 as an Easter egg
• Developer using 418 to mark intentionally unavailable endpoints
• Load balancer or WAF returning 418 for blocked requests (non-standard usage)
• Testing or demonstration purposes

Steps

1. 1If you receive 418 from a real API, the endpoint is intentionally blocked or disabled
2. 2Try google.com/teapot for a fun example of a 418 response
3. 3Do not use 418 in production APIs for real error conditions — use proper HTTP status codes
4. 4If a WAF returns 418, check if your request is being blocked as suspicious
5. 5Contact the API provider if you receive 418 on a supposedly functional endpoint

Tags

More in 4xx Client Error

Frequently Asked Questions