vøiddo
tool · dev / debug

@v0idd0/httpwut.

explain HTTP responses with the actual rfc reference.

pipe curl into httpwut. get a one-paragraph explainer for the status code + the headers worth looking at + the rfc section you should actually read.

npm i -g @v0idd0/httpwut
github → npm mit · free forever
httpwut icon
what it does

no more guessing what “418 — i’m a teapot” anymore.

four jobs. all in your terminal. no api call, no internet round-trip — just a plain tool that does what it says.

explain a response

$ curl -I voiddo.com | httpwut
200 OK
cf-cache-status: HIT
→ served from cloudflare edge
rfc 9110 §15.3.1

look up a code

$ httpwut 429
429 too many requests
→ rate-limit signal
respect Retry-After
rfc 6585 §4

explain a header

$ httpwut 'strict-transport-security'
HSTS
→ force https forever
rfc 6797

diff two responses

$ httpwut diff a.txt b.txt
+ cf-cache-status: HIT
- cf-cache-status: MISS
(now cached)
install

three ways. all painless.

npm

$ npm i -g @v0idd0/httpwut

node 14+ on linux / macos / windows. updates with npm update -g.

github releases

$ curl -L github.com/voidd0/httpwut/releases/latest

single static binary. zero runtime needed. all releases →

git clone

$ git clone github.com/voidd0/httpwut

read the source, send a pr, fork it. mit licence, no cla. repo →

why we built it

stack overflow tells you what 404 means. but httpwut tells you why your server is returning 400 with no body, and points you at rfc 9110 §15.5.1 instead of a 12-year-old answer.

no telemetry. no signup. all rfcs vendored locally — works offline on a plane. mit forever, even if vøiddo dies tomorrow.

star on github → httpwut vs HTTPie → all tools

power user?

use this daily? tools.voiddo Pro · $9 one-time

supports 66 free tools · Pro license via Paddle · one flat price, no subscription