Reference

Lookup tables you can check without opening a spec: HTTP status codes, TCP/UDP ports, the ASCII table, HTML entities, and emoji shortcodes — each with notes worth having.

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? Which well-known ports should never be exposed to the public internet? What is the hex value for a backspace? What is the entity name for a non-breaking space? What is the shortcode for that emoji?

These references answer those questions in a few seconds, and give you more than a bare number or name: status codes come with common scenarios and recommended fixes, ports with protocol notes and exposure risk, code points and entities with every base and a copyable form — and each entry traces back to the standard it came from.

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. ASCII and HTML entities

    All 128 ASCII code points plus the Latin-1 extension, each with its decimal, hex, octal, and binary value, its glyph, and a C escape where one exists — alongside more than fifteen hundred HTML entities, grouped by category and ready to copy.

  4. Emoji shortcodes

    More than eighteen hundred emoji across nine categories, searchable, with the emoji itself, its GitHub shortcode, code point, or HTML entity a click away.