Post

Have you seen testserver.host/? As part of building HTTP Toolkit I often need a remote servers for testing edge cases, so I've built one! Now fairly mature & stable. It's httpbin.org plus badssl.com plus lots of extras.

testserver.hostTestserverEndpoints can be combined using double-dashes, e.g. expired--revoked--http2--tls-v1-2.{domain} will return an expired and revoked certificate, use TLSv1.2, and then negotiate HTTP/2 on the connection.

30/6/26, 11:16 am2 reposts4 likes

HTTP Toolkit

@httptoolkit.com

30 June

Extras you say? * More endpoints, like /echo (echoes back raw HTTP), /encoding/zstd, and /error/reset * Websocket support * Faster & more reliable than either * Combining HTTP & TLS tests (give me an expired cert, then a 404 response) * Chainable endpoints, for both HTTP & TLS

HTTP Toolkit

@httptoolkit.com

30 June

Faster & more reliable? 1. Horizontal autoscaling & globally distributed: low latency everywhere, failover, easy to scale. 2. Cert issuance 100% automated, with ACME and a local CA (many badssl cases need manual setup, and so rot: failing due to expiry, not the real cause).

HTTP Toolkit

@httptoolkit.com

30 June

End result: on my local machine & wifi, curl -kv expired.badssl.com/ takes more than a second, and httpbin.org/anything takes 2.2s. expired.testserver.host/anything takes about 150ms 🚀

httpbin.orghttpbin.org

HTTP Toolkit

@httptoolkit.com

30 June

Chainable endpoints? HTTP: testserver.host/info/123/delay/1/status/404 - return a 123 intermediate status, wait 1 second, then return a 404 TLS: incomplete-chain--expired--http2.testserver.host: give me an expired cert, missing the intermediate cert in the chain, and exclusively negotiate HTTP/2.

testserver.hosttestserver.host