HTTP Testbed

Return any status, delay, redirect or payload size to exercise client retry and timeout logic.

A set of free HTTP test endpoints you can call straight from curl: return any status code, delay for N seconds, chain redirects, return a payload of a given size, gzip, ETag and cache headers, Basic/Bearer auth. Use them to check how your client behaves around timeouts, retries, redirects and caching.

How to use

  1. Pick an endpoint from the table and hit “Try” to see the real response.
  2. Or append the path to the base URL and call it with curl or Postman.
  3. Change the number in the path as needed, e.g. /hb/status/503 or /hb/delay/5.

FAQ

Why is there no /redirect-to?
Because it is an open redirect. Allowing an arbitrary external URL as the redirect target turns this site into a springboard for phishing links, and a domain blacklisted by security vendors is very hard to recover. The self-contained /hb/redirect/{n} only redirects within this service, which is safe and sufficient.
Why are delay and size capped?
These endpoints are public: long delays hold connections open and large responses burn egress bandwidth — both are real costs and easy to abuse as free bandwidth. The caps are 10 seconds, 1MB and 10 redirects; anything larger is clamped rather than rejected.
How does this differ from httpbin.org?
It is a deliberately safer subset: the open redirect and the endpoint that leaks server environment variables are removed, and delay and size have hard caps. In exchange it is same-origin with the rest of Zapbox, under our control, and every trade-off is documented.

Related tools