HTTP status codes for website checks and integrations
The status code describes the result of an HTTP request. A friendly error page that returns 200 is different from a real 404. Read the code, method and response headers together when testing a website or API.
HTTP status codes for website checks and integrations
| Code | Meaning | Practical interpretation |
|---|---|---|
| 200 | OK | Request succeeded; interpret the body according to the request method. |
| 201 | Created | Request created one or more resources. |
| 204 | No Content | Successful request with no response content. |
| 301 | Moved Permanently | Resource has a permanent new URI; some clients may change POST to GET. |
| 302 | Found | Temporary redirect; some clients may change POST to GET. |
| 307 | Temporary Redirect | Temporary redirect that preserves the request method. |
| 308 | Permanent Redirect | Permanent redirect that preserves the request method. |
| 304 | Not Modified | Conditional GET or HEAD can reuse its stored representation. |
| 400 | Bad Request | Server cannot or will not process the request because of a perceived client error. |
| 401 | Unauthorized | Valid authentication credentials are required. |
| 403 | Forbidden | Server understands the request but refuses it. |
| 404 | Not Found | No current representation was found, or the server will not disclose one. |
| 405 | Method Not Allowed | The method is known but is not supported for this target resource. |
| 410 | Gone | Access is no longer available and the condition is likely permanent. |
| 429 | Too Many Requests | Request rate is limited; Retry-After may be supplied. |
| 500 | Internal Server Error | Unexpected server condition prevented fulfillment. |
| 502 | Bad Gateway | A gateway received an invalid upstream response. |
| 503 | Service Unavailable | Server is temporarily unable to handle the request. |
| 504 | Gateway Timeout | A gateway did not receive an upstream response in time. |
Formula & method
Inspect the status before parsing a response as the expected document or JSON payload. Follow a redirect intentionally and record its chain when verifying canonical URLs. For a deleted page, check both the visible message and the actual HTTP status.
Authentication, rate limits and temporary failures require different handling. A 429 or 503 may provide Retry-After; respect it rather than retrying rapidly. Applications can still report a business-level failure inside a 200 response, so the status alone does not validate the entire operation.
Worked example
If an unknown URL shows “Page not found” but responds with 200, the visible copy and protocol result disagree. A custom error design can still return the correct 404 status.
What can change the answer
This table summarizes selected standard meanings, not every status code or application contract. Do not infer that a 403 or 404 proves a resource never existed.
Sources & definitions
Method checked:
Continue with a related task
Page View Revenue Calculator
Page views equal visits multiplied by pages per visit. Estimated revenue equals those page views divided by 1,000, multiplied by page RPM.
Cache Origin Savings Calculator
Expected origin requests equal total requests multiplied by one minus the cache-hit fraction. At 80% hits, 100,000 requests leave 20,000 expected origin fetches.
Uptime Downtime Budget Calculator
Allowed downtime equals the monitoring window multiplied by one minus the uptime target. A 99.9% target over 30 days allows 43.2 minutes in this time-based model.
Observed Uptime Calculator
Observed uptime equals monitored time minus downtime, divided by monitored time, multiplied by 100. Use downtime measured within the same monitoring window.