API Documentation
Home > Knowledge Base > ADCaaS - Load Balancing, DNS > What HTTP response codes do you support for monitoring server availability?

What HTTP response codes do you support for monitoring server availability?


We support the following list of response codes which can be used individually or together to determine the state of a server.

100 – Continue
101 – Switching Protocols
200 – OK
201 – Created
202 – Accepted
203 – Authoritative Information
204 – No Content
205 – Reset Content
206 – Partial Content
300 – Multiple Choices
301 – Moved Permanently
302 – Found
303 – See Other
304 – Not Modified
305 – Use Proxy
307 – Temporary Redirect
400 – Bad Request
401 – Unauthorized
402 – Payment Required
403 – Forbidden
404 – Not Found
405 – Method Not Allowed
406 – Not Acceptable
407 – Proxy Authentication Required
408 – Request Time-Out
409 – Conflict
410 – Gone
411 – Length Required
412 – Precondition Failed
413 – Request Entity Too Large
414 – Request-URI Too Large
415 – Unsupported Media Type
416 – Requested Range Not Satisfiable
417 – Exception Failed
500 – Internal Server Error
501 – Not Implemented
502 – Bad Gateway
503 – Service Unavailable
504 – Gateway Time-Out
505 – HTTP Version Not Supported

If you need assistance determining what HTTP response code might be best for your particular situation, just create a support case. We’re here to help and we’re fast too!

Upgrade to reliable DNS!

TRY IT FREE