Test if HTTP keep-alive works. Connection reuse and timing.
The HTTP Keep-Alive Tester sends multiple requests to a URL and checks whether the connection is reused (keep-alive) or closed after each request. Developers use it to verify server and proxy keep-alive settings, to debug "too many connections" by confirming reuse, or to measure the effect of keep-alive on latency. May show connection count and timing.
HTTP keep-alive (Connection: keep-alive) allows multiple requests on the same TCP connection instead of opening a new one each time.
Some servers or proxies disable it for security or resource limits; others close after a timeout or number of requests.
Browsers manage connections; a server-side or dedicated client test gives clearer control and visibility.
It sends a small number of requests; impact is minimal.
HTTP/2 multiplexes over one connection by default; keep-alive is less of a concern but still relevant for HTTP/1.1.