Skip to content

HTTP Status Code Lookup

Enter an HTTP status code to get its name, description, common causes, and how to fix it. Covers all standard codes (1xx through 5xx) plus unofficial Cloudflare and Nginx codes.

Required

Enter a status code between 100 and 599

Get an API key to automate this

Result


                    

Code snippets


                                                

                                                

                                                

                                            

What this tool checks

  • All standard HTTP status codes (100-511)
  • Unofficial codes (418, 420, 444, 499, 520-527)
  • Common causes for each error
  • How-to-fix suggestions
  • RFC specification references
  • Category and cacheability info

Automate this with the API

Run this tool programmatically from your code. Get a free temporary API key with 20 requests/day — or register for 75 requests/day.

curl https://apixies.io/api/v1/http-status?code=... \ -H "X-API-Key: YOUR_API_KEY"

Frequently asked questions

What HTTP status codes does this cover?
All standard codes from RFC 7231 and related RFCs (100-511), plus commonly used unofficial codes from Cloudflare (520-527), Nginx (444, 499), and Twitter (420).
What is the difference between 401 and 403?
401 means the request lacks valid authentication credentials. 403 means the server understood the request but refuses to authorize it, even with valid credentials. Think of 401 as "who are you?" and 403 as "you can't do that."
Why do I keep getting 429 errors?
429 means you're sending too many requests. Implement exponential backoff, check the Retry-After header, and consider batching requests or requesting higher rate limits from the API provider.

We use cookies for analytics to understand how our site is used. Privacy Policy