HTTP 418 I'm a teapot
Famous internet easter egg used across mock APIs, developer culture, and humorous tests.
4xx Client Errors
RFC 2324 / RFC 9110 Section 15.5.19
Test endpoint:
curl -i -X GET https://httpbin.org/status/418 ⚠️ Common Causes
- • Attempting to brew coffee using a teapot under HTCPCP RFC 2324
- • Easter egg in developer mock service
🛠️ How to Fix / Developer Actions
- ✓ Brew tea instead of coffee 🫖
- ✓ Informational easter egg; replace with standard 400 or 200 in production
Open the full tool: Convert cURL to Fetch, Python, or Go →
Status Reference & Causes
4xx Client Errors Status Codes Table
| Код | Название | RFC |
|---|---|---|
| 400 | Bad Request | RFC 9110 Section 15.5.1 |
| 401 | Unauthorized | RFC 9110 Section 15.5.2 |
| 403 | Forbidden | RFC 9110 Section 15.5.4 |
| 404 | Not Found | RFC 9110 Section 15.5.5 |
| 405 | Method Not Allowed | RFC 9110 Section 15.5.6 |
| 408 | Request Timeout | RFC 9110 Section 15.5.9 |
| 409 | Conflict | RFC 9110 Section 15.5.10 |
| 410 | Gone | RFC 9110 Section 15.5.11 |
| 418 | I'm a teapot | RFC 2324 / RFC 9110 Section 15.5.19 |
| 422 | Unprocessable Content | RFC 9110 Section 15.5.21 |
| 429 | Too Many Requests | RFC 6585 Section 4 |
FAQ
What does HTTP 418 I'm a teapot mean?
Famous internet easter egg used across mock APIs, developer culture, and humorous tests. It is defined in RFC 2324 / RFC 9110 Section 15.5.19 as a 4xx Client Errors status code.
Is HTTP 418 an error on client or server side?
HTTP 418 is a client-side error (4xx), meaning the request itself was invalid, unauthorized, or malformed.
How can I test an HTTP 418 response in terminal?
You can use cURL with the -I flag to fetch headers only: curl -I https://httpbin.org/status/418