Every protocol.
One place.

The most comprehensive, structured, and developer-friendly reference for communication protocols.

Search protocols, codes, headers, RFCs...⌘K

57+

ProtocolsDocumented

887+

Codes &Status Definitions

Layers ofCoverage

Always

Free & Openfor Everyone

5 Layers57+ Protocols887+ CodesAlways Free

Quick lookups

Code	Status	Meaning	Defined In	Common In
100	Continue	HTTP 100 Continue indicates the server has received the request headers and the client should proceed to send the request body.	RFC 9110	Large file uploads, APIs
101	Switching Protocols	HTTP 101 Switching Protocols indicates the server is switching to a different protocol as requested by the client via the Upgrade header.	RFC 9110	WebSocket upgrades
102	Processing	HTTP 102 Processing is a WebDAV status code that indicates the server has received and is processing a long-running request, but has not yet completed it.	RFC 4918	WebDAV servers, long-running server operations
103	Early Hints	HTTP 103 Early Hints is an informational response that sends preliminary headers (typically Link preload directives) before the final response.	RFC 8297	CDNs, server-rendered web apps, performance optimization, edge networks
200	OK	HTTP 200 OK indicates the request has succeeded.	RFC 9110	All APIs, Browsers
201	Created	HTTP 201 Created indicates the request has been fulfilled and one or more new resources have been created.	RFC 9110	REST APIs

AuthoritativeSourced from RFCs, specifications, and official documentation.

StructuredEvery protocol follows the same clear, predictable structure.

Up to dateContinuously updated as standards evolve and new protocols emerge.

OpenFree to use, open to contribute, built for the engineering community.

Developer firstExamples, diagrams, and references designed for engineers.