Instant lookup for 1xx-5xx HTTP status codes, RFC 9110 semantics, cacheability, and retry rules.
Rate limit exceeded. Respect Retry-After header with exponential backoff + jitter.
{ "status": 429, "error": "Too Many Requests", "message": "Rate limit exceeded. Respect Retry-After header with exponential backoff + jitter.", "retryable": true, "spec": "RFC 6585" }
Initial request headers received; client may proceed sending request body.
Server agrees to upgrade connection protocol (e.g., HTTP/1.1 -> WebSocket).
Sends Link preload headers before final response is ready.
Request succeeded cleanly and response body holds requested representation.
Request succeeded and created one or more new resources (often paired with Location header).
Request accepted for async background processing; outcome is pending.
Succeeded with intentionally empty response body (common for DELETE/PUT/OPTIONS).
Delivering requested byte range for resumable downloads or media streaming.
Target resource permanently relocated to Location URI (SEO link equity passes).
Temporary redirect; browsers may rewrite POST to GET unless 307 is used.
Cached representation still matches ETag or If-Modified-Since; no body sent.
Temporary redirect that strictly preserves original HTTP method and body.
Permanent redirect that strictly preserves HTTP method (preferred over 301 for APIs).
Malformed syntax, invalid JSON, missing fields, or failed schema validation.
Missing or invalid authentication credentials (JWT/API key expired or absent).
Identity is known, but lacks permission/scope/ACL or blocked by WAF.
Origin could not find requested route or entity ID.
Endpoint exists, but HTTP verb (GET/POST/DELETE) is unsupported; check Allow header.
Server closed idle connection before client finished sending complete request.
Request conflicts with current resource state (duplicate key, version/ETag mismatch).
Resource permanently deleted and will not return (de-indexes faster than 404).
Payload exceeds server or proxy limit (check Nginx client_max_body_size).
Request Content-Type header (e.g., text/plain vs application/json) rejected.
April Fools HTCPCP status code reserved permanently in RFC 9110.
Syntax is valid JSON/XML, but domain/semantic validation rules failed.
Blocked due to government censorship, DMCA, or court order.
Unhandled exception or crash on the origin application server.
Reverse proxy/gateway received invalid, empty, or refused response from upstream.
Server temporarily overloaded or in maintenance mode; check Retry-After header.
Reverse proxy waited too long for upstream application to respond.
Cloudflare-specific: origin returned empty/unexpected response or closed TCP.
Cloudflare-specific: TCP handshake to origin server timed out (firewall/overload).
Cloudflare-specific: origin connected, but took >100s without sending HTTP response.
Pin this tool to your browser side panel
Access this utility anytime with Alt+M without switching tabs. 100% offline & free.
This RFC 9110 and edge status catalog runs locally in your browser memory for instant incident response.
MiniToolDesk is 100% free and client-side. Your support keeps the web ad-free.
Beautify, format, and indent messy SQL queries across MySQL, Postgres, SQLite in local memory
Safely decode, verify, and inspect JSON Web Tokens (JWT) payload and headers in local memory
Convert YAML to JSON and JSON to YAML bidirectionally with real-time validation
Convert Data Storage (KB/KiB, MB/MiB, GB/GiB), CSS units (px to rem), Length, Speed, and Temp