On April 1, 1998, Larry Masinter published RFC 2324.
It defined the Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) — a complete, properly formatted internet standard for controlling coffee pots over HTTP. It introduced a new HTTP method: BREW. It introduced request headers like Accept-Additions: milk; 1. It introduced Content-Type: message/coffeepot.
Most importantly, it introduced HTTP 418.
Section 2.3.2: "Any attempt to brew coffee with a teapot should result in the error code '418 I'm a Teapot'. The resulting entity body MAY be short and stout."
It was a joke. The internet kept it anyway.
Twenty-eight years later, 418 I'm a Teapot still exists in every HTTP standard, every browser, every HTTP library. Larry Masinter accidentally created the most beloved useless status code in internet history.
I built the official compliance checker.
"Is your server RFC 2324 compliant? Does it know it's a teapot?"
What I Built
The RFC 2324 Compliance Checker tests any URL for HTCPCP compliance — specifically, whether it returns 418 I'm a Teapot when asked to brew coffee.
Enter any URL. The checker sends a simulated BREW request. The result:
If the server returns 418: A gold compliance certificate. "This endpoint is RFC 2324 certified. It knows it is a teapot." Certified date: April 1, 1998 (retroactively).
If the server returns anything else: A red violation report. "This server would brew coffee. RFC 2324 violation. HTTP [status] — this server does not know it is a teapot."
The only RFC 2324 compliant URL in the world is /.netlify/functions/brew — the endpoint on this very app, which returns a real HTTP 418 response. Every other website fails.
The Actual 418 Endpoint
This is the technical centerpiece. The deployed app has a Netlify Function that returns a genuine HTTP 418:
curl -i https://your-site.netlify.app/.netlify/functions/brew
HTTP/2 418
content-type: application/json
x-rfc: 2324
x-teapot: true
x-can-brew-coffee: false
x-compliance: RFC-2324-CERTIFIED
{"status":418,"error":"I'm a teapot","shortAndStout":true,"canBrewCoffee":false}
That is a real HTTP 418. You can curl it. The judges can curl it. It has the custom headers from RFC 2324. It works.
The Joke Has a Point
The challenge prompt says "HTCPCP IYKYK." Most people don't know what HTCPCP is. They see the teapot emoji and move on.
If you know — if you've encountered 418 in a status code list and wondered why a teapot is in there — this project is for you. It's a love letter to a 28-year-old April Fools joke that became permanent infrastructure.
The compliance checker is deadpan by design. The certificate is formatted like a real compliance document. The violation report cites the RFC section. The explainer at the bottom tells you who Larry Masinter is and why his joke is still in your browser.
The humor is for people who know. That's the whole IYKYK.
Demo
Try RFC 2324 Checker Live →** https://rfc-compliance-checker.netlify.app/
1. Open the checker
Clean, minimal UI. An input field. A "Check" button. A row of example URLs to try.
2. Try google.com
"BREW /coffee HTCPCP/1.0 → HTTP 200 — VIOLATION. This server would brew coffee."
3. Try /.netlify/functions/brew
"HTTP 418 I'm a Teapot — RFC 2324 COMPLIANT. This endpoint knows it is a teapot."
Gold certificate. Certification date: April 1, 1998. Larry Masinter citation.
4. Try anything else
They all fail. The entire internet fails. Only the teapot passes.
How I Built It
Stack: React 19 + Vite + Tailwind CSS v4
Real 418: Netlify Function (one file)
Since browsers can't ping arbitrary external URLs without CORS headers, the checker simulates responses for external URLs — all fail, as they should. For the app's own /brew endpoint, it makes a real fetch that returns real 418.
The HTCPCP request display in the UI is taken directly from RFC 2324 section 2.1. I read the entire RFC. It's genuinely well-written for an April Fools document. Larry Masinter put work in.
Prize Category
I'm submitting for Best Ode to Larry Masinter.
This project exists entirely because of RFC 2324. The checker tests whether a URL knows it is a teapot — the exact premise of Masinter's 1998 April Fools spec. I read the full RFC before writing a single line of code. The HTCPCP request display uses the exact headers from RFC 2324 section 2.1. The explainer panel quotes section 2.3.2 verbatim.
The deeper tribute is the deployed /brew endpoint that returns a genuine HTTP 418 with X-RFC: 2324 and X-Can-Brew-Coffee: false headers. Twenty-eight years after Masinter wrote his joke, this URL proves his point: a teapot should return 418. It does. You can curl it.
The RFC 2324 Compliance Certificate — issued retroactively from April 1, 1998 — is the punchline. The only compliant website in the world is this one, because we built it to be. Everything else would brew coffee. That's the violation.
What I Learned
Reading RFC 2324 carefully is worth it.
The document is internally consistent. The protocol design is real — it's not just a fake spec with 418 bolted on. There are request headers, response semantics, error codes, and implementation notes. Masinter wrote it as a proper RFC, just for a coffee pot.
The joke works because the execution is sincere. The RFC 2324 Compliance Checker works the same way — it's a real compliance tool, just for an imaginary protocol.
Sincerity is the secret ingredient in good April Fools builds.
🫖 Try RFC 2324 Checker Live → https://rfc-compliance-checker.netlify.app/
💻 Source on GitHub → https://github.com/pulkitgovrani/rfc2324-compilechecker
📄 Read RFC 2324 → https://www.rfc-editor.org/rfc/rfc2324
RFC 2324 Compliance Authority — Certifying teapots since April 1, 1998.
Top comments (0)