HTTP Status Reference
RFC 9110Searchable reference for standard HTTP status codes with usage and caching guidance.
- Searchable
- Client-Side Only
Search HTTP statuses
Search by code, phrase, class, description, or when-to-use guidance.
Status codes
Showing all HTTP status codes.
Class meanings
| Class | Meaning | Typical use |
|---|---|---|
1xx | Informational | Interim responses while a request continues. |
2xx | Successful | The request was received, understood, and accepted. |
3xx | Redirection | The client needs another request or cached representation. |
4xx | Client Error | The request has a client-side problem or cannot be fulfilled. |
5xx | Server Error | The server failed to fulfill an apparently valid request. |
Safety, idempotency, and caching
Status codes do not make a request safe or idempotent by themselves. Safety and idempotency come from the request method and application semantics.
RFC caching rules allow some responses to be reused by default, including common statuses such as 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, and 501. Other statuses generally need explicit cache headers.
Related Tools
Curl Studio
Parse and generate curl commands.
Protocol Header Visualizer
Interactive bit-level diagrams for Ethernet, IPv4, IPv6, TCP, UDP, ICMP, and ARP.
DNS Record Reference
Interactive reference for DNS record types with syntax, examples, and command builders.
Port Reference
Searchable IANA port database with security risk levels and protocol filters.