Skip to content

Expected HTTP Status Ranges

Expected status ranges let teams decide what a healthy HTTP or keyword response actually means for each endpoint.

Get StartedAll features
Expected HTTP Status Ranges — WebGuard

At a glance

  • Supports comma-separated codes and ranges
  • Defaults can stay broad or be tightened per monitor
  • Works with HTTP and keyword checks

How it helps

Use expected HTTP status ranges when redirects, accepted asynchronous responses, or strict success-only endpoints need different rules.

Examples such as 200-299, 301, and 302 let you keep normal behavior healthy while still detecting unexpected client or server errors.

These expectations reduce false positives while preserving precise incident signals for endpoints with known response behavior.

Frequently asked questions

What is Expected HTTP Status Ranges?

Expected status ranges let teams decide what a healthy HTTP or keyword response actually means for each endpoint.

Who is Expected HTTP Status Ranges for?

Use expected HTTP status ranges when redirects, accepted asynchronous responses, or strict success-only endpoints need different rules.

What does Expected HTTP Status Ranges provide?

Supports comma-separated codes and ranges Defaults can stay broad or be tightened per monitor Works with HTTP and keyword checks