Success
200 200 OK
The request succeeded and the server returned the page or data you asked for. This is the response a healthy website gives for every normal page view.
Common causes
- Nothing is wrong — but a 200 on a page that should have failed is its own problem.
- Some applications return 200 with an error message in the body, a "soft 404", which hides broken pages from monitoring and keeps dead URLs in search results.
How to fix it
- If you are seeing 200 where you expected an error, make sure your application sets the status code as well as rendering the error text.
See what a site actually returns
Run a live check and read the real status code, headers and timings.
Other status codes
201 Created
204 No Content
206 Partial Content
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
307 Temporary Redirect
308 Permanent Redirect
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
405 Method Not Allowed
408 Request Timeout
410 Gone
413 Payload Too Large
418 I'm a Teapot
429 Too Many Requests
451 Unavailable For Legal Reasons
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
507 Insufficient Storage
508 Loop Detected
521 Web Server Is Down
522 Connection Timed Out
523 Origin Is Unreachable
525 SSL Handshake Failed