Reference

Developer references for HTTP status codes and TCP/UDP port numbers across API debugging, website troubleshooting, firewall configuration, and security audits.

5 tools

Reference

About this category

Some answers you just need to look up. Which HTTP status code is right for a stale resource? What port does PostgreSQL listen on? Is 503 retryable? Which well-known ports should never be exposed to the public internet?

These references answer those questions in a few seconds, with the context you actually need around the bare number — common scenarios, recommended fixes, related codes or ports, and the source standard.

What you can do here

  1. HTTP status reference

    Every HTTP status code with a one-line meaning, common scenarios, recommended fixes, retry semantics, and links to the spec.

  2. TCP/UDP port reference

    Well-known and registered ports with the service they belong to, protocol notes, risk level, and exposure recommendations.

  3. Searchable and filterable

    Filter by category (1xx–5xx) or protocol (TCP/UDP/SCTP), search by number, phrase, or service name to land on the right entry quickly.

  4. Pragmatic, opinionated notes

    Each entry is more than a definition — it includes the kind of context you'd only get from someone who has shipped the thing.