Search for a command to run...
Search and filter common HTTP status codes with bilingual explanations, categories and troubleshooting hints.
Runs locally in your browser by default — nothing is uploaded first.
Client should continue the request.
Client should continue the request.
Server accepted the protocol switch.
The request completed successfully.
A new resource was created.
The request was accepted for processing.
Request succeeded with no response body.
Resource has a new permanent URL.
Temporary redirect to another URL.
Cached version is still valid.
Repeat the request at another URL without changing method.
Repeat the request at a new URL without changing method.
The server could not understand the request.
Authentication is required.
The server understood the request but refused it.
The requested resource was not found.
The HTTP method is not allowed for this resource.
The server timed out waiting for the request.
The request conflicts with the current state.
The resource is no longer available.
The request body is larger than the server allows.
The content type is not supported.
The request syntax is valid but semantic validation failed.
You have hit a rate limit.
The server encountered an unexpected error.
The server does not support this capability.
An upstream server returned an invalid response.
The server is temporarily unavailable.
An upstream server timed out.
HTTP Status Code Lookup runs locally in your browser by default, so you can work with the content without uploading it first.
Look up common HTTP status codes with categories, explanations and quick debugging hints.
Does HTTP Status Code Lookup run locally or in the cloud?
HTTP Status Code Lookup runs locally in your browser by default, so you can work with the content without uploading it first.
What usually comes after HTTP Status Code Lookup?
A common next step is to continue into related workflows such as Code and Data Formatting Tools.
Is a JWT encrypted?
A standard signed JWT is not. The payload is base64url text that anyone with the token can read. Encryption requires the separate JWE format.
A JWT is three base64url segments, and decoding one tells you nothing about whether it is genuine. How to read the claims, and why tokens break in URLs.
Base64 Explained: Encoding, Padding, Data URLs, and Common MistakesA technical article on how Base64 turns bytes into text, why padding exists, how URL-safe variants differ, and why Base64 is not encryption.
Encryption Basics in the Browser: Hashing, Symmetric Keys and What Stays LocalHashing is not encryption. Symmetric encryption needs a secret both sides share. What browser-side crypto can and cannot protect.
collectionCode and Data Formatting ToolscollectionNetwork and DevOps ToolscollectionNetwork Operations ToolsLook up common HTTP status codes with categories, explanations and quick debugging hints.
