HTTP/TCP/TLS Testserver

Part of HTTP Toolkit: powerful tools for building, testing & debugging HTTP(S)

A public test server for HTTP & related protocols (similar to httpbin.org and badssl.com) but actively maintained, reliable & fast.

It provides configurable endpoints to inspect requests, return custom HTTP & WebSocket responses, and serve TLS certificates in a wide range of valid & invalid configurations.

The server with full endpoint documentation is live at testserver.host.

Self-hosting

A public container image is published to Docker Hub (and mirrored to ghcr.io/httptoolkit/testserver):

docker run -p 3000:3000 httptoolkit/testserver

This is usable with no configuration, serving TLS with a self-signed local CA for localhost. For advanced functionality (especially ACME, to get a publicly trusted CA cert) configure via environment variables:

• PORTS - comma-separated ports to listen on (default 3000)
• ROOT_DOMAIN - the domain being served (default localhost)
• ACME_PROVIDER - obtain real certificates via ACME: letsencrypt, zerossl or google (omit for a self-signed local CA)
• ACME_ACCOUNT_KEY - ACME account key in PEM format; required when ACME_PROVIDER is set
• CERT_CACHE_DIR - directory to persist issued certificates; required for ACME (the image defaults this to /usr/src/app/cert_dir)
• PROACTIVE_CERT_DOMAINS - comma-separated domains to fetch certificates for on startup
• LOCAL_CA_KEY / LOCAL_CA_CERT - pin the local CA in PEM format; generated fresh if unset
• DNS_SERVER - set true to run the built-in DNS server for wildcard (DNS-01) certs (needs UDP port 53)
• TRUST_PROXY_PROTOCOL - set true to honour PROXY protocol headers
• METRICS_PORT - port to expose Prometheus metrics on