Skip to content
IPOK

HTTP Status Codes (Quick Reference)

What do 200, 301, 403, 404, 502 mean? This tool lists common HTTP status codes from 1xx–5xx (including Cloudflare's 520–526), each with the standard phrase and a one-line explanation — search by number or keyword to find it instantly.

Worth noting: when 403 (Forbidden), 429 (Too Many Requests) or 503 (Unavailable) keep showing up, it's often not your code but your exit IP being rate-limited / blocked — datacenter / proxy IPs trip these especially. So if you keep hitting them, check whether your exit IP is clean.

100
Continue
Server received headers; client should continue sending the body.
101
Switching Protocols
Server agrees to switch protocols (e.g. to WebSocket).
103
Early Hints
Preliminary headers so the browser can start preloading.
200
OK
Standard success response.
201
Created
Request succeeded and a new resource was created.
202
Accepted
Request accepted but not yet processed (async).
204
No Content
Success with no response body (common for DELETE).
206
Partial Content
Returned a requested range (resumable download / video seek).
301
Moved Permanently
Resource permanently moved (passes SEO weight).
302
Found
Resource temporarily elsewhere (no SEO transfer).
303
See Other
Fetch the result from another URL via GET.
304
Not Modified
Not changed; use your cached copy.
307
Temporary Redirect
Like 302 but strictly keeps the method.
308
Permanent Redirect
Like 301 but strictly keeps the method.
400
Bad Request
Malformed request the server can't understand.
401
Unauthorized
Authentication required or failed.
403
Forbidden
Authenticated but not allowed — often the exit IP is blocked / geo-restricted.
404
Not Found
Resource doesn't exist or wrong URL.
405
Method Not Allowed
HTTP method not supported on this URL.
408
Request Timeout
Server timed out waiting for the request.
409
Conflict
Conflict with the current resource state.
410
Gone
Resource existed but is permanently gone.
413
Payload Too Large
Upload exceeds the server's size limit.
415
Unsupported Media Type
The Content-Type isn't accepted.
418
I'm a teapot
An April Fools' joke, sometimes used as a playful refusal.
422
Unprocessable Entity
Syntax OK but semantically invalid (validation failed).
429
Too Many Requests
Rate-limited — often the same exit IP hit too often.
431
Request Header Fields Too Large
Headers (e.g. cookies) too large.
451
Unavailable For Legal Reasons
Blocked for legal / censorship reasons.
500
Internal Server Error
Generic server-side error (the most common 5xx).
501
Not Implemented
Server doesn't support the functionality.
502
Bad Gateway
Upstream / backend returned an invalid response.
503
Service Unavailable
Server overloaded or under maintenance.
504
Gateway Timeout
Gateway timed out waiting for the upstream.
511
Network Authentication Required
Captive portal: network login required.
520
Web Server Returned an Unknown Error
Cloudflare: origin returned an unexpected response.
521
Web Server Is Down
Cloudflare: the origin server refused the connection.
522
Connection Timed Out
Cloudflare: TCP connection to the origin timed out.
523
Origin Is Unreachable
Cloudflare: the origin is unreachable.
524
A Timeout Occurred
Cloudflare: connected but the origin didn't reply in time.
525
SSL Handshake Failed
Cloudflare: SSL handshake with the origin failed.
526
Invalid SSL Certificate
Cloudflare: the origin's SSL certificate is invalid.

An HTTP status code is the server's one-line receipt for each request. Worth noting: frequent 403 / 429 often isn't a code bug but your exit IP being rate-limited / blocked.

Getting 403 / 429 a lot? Check if your exit IP is clean →
Check your own IP — purity, risk score, native vs datacenter, leaksCheck IP →

FAQ

What's the difference between 403 and 404?

404 means the resource doesn't exist; 403 means it exists but you're not allowed — could be permissions, but often the exit IP is blocked / geo-restricted.

How do 502 / 503 / 504 differ?

502: the gateway got an invalid response from upstream; 503: the server is overloaded or under maintenance; 504: the gateway timed out waiting for upstream. All server-side.

What are 520–526?

These are Cloudflare's custom codes indicating a problem between CF and the origin (origin down / timeout / invalid cert), not standard HTTP codes.

More tools