Post

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

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).

30/6/26, 11:16 am0 reposts0 likes

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

testserver.hosttestserver.host

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.

revoked.testserver.hostrevoked.testserver.host

And combine them too! revoked--tls-v1-2.testserver.host/ws/message/hello/message/goodbye/close A websocket server that only supports TLS v1.2 and uses a revoked certificate - once you connect, it sends hello, then sends goodbye, then closes the connection.