UUID Studio

UUID Studio

HTTP Status Code Lookup

Look up what an HTTP status code actually means.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • Not Found 
    404
  • Internal Server Error 
    500

About HTTP Status Code Lookup

Most developers have 200, 404, and 500 memorized, but the long tail - 409, 422, 429, 503 - gets confused often enough that a quick lookup beats guessing from memory or half-remembering which RFC it's from.

Enter a status code and get its standard name and a plain-language description of when it's used, or leave the input blank to see the full list of commonly used codes at a glance.

This covers the codes developers actually encounter day to day, not the complete IANA registry - for the full authoritative list, the HTTP status code registry itself is the source of truth.

FAQ

What's the difference between 401 and 403?
401 Unauthorized means authentication is missing or invalid - the client needs to log in. 403 Forbidden means the server understood who you are but you don't have permission for that specific resource.
Is 422 the same as 400?
Both indicate a client-side problem, but 400 Bad Request usually means malformed syntax the server couldn't parse at all, while 422 Unprocessable Entity means the request was well-formed but failed validation rules.