CH-J Server Managerserver management over SSH
Menu
Guides for specific tasks →

HTTP/2, HTTP/3 and TLS diagnostics

Check the actual HTTP protocol with the bundled client and inspect TLS 1.2/1.3.

What you need

A supported system and reachable target. The HTTP client and CA store are bundled. QUIC requires the target HTTPS service’s UDP port.

Procedure

  1. After unlocking the vault, open Server Diagnostics. Enter a hostname, IPv4, IPv6 or URL and select Auto, IPv4, IPv6 or Both.
  2. Run the protocol comparison in HTTP. Distinguish the requested version, the protocol actually negotiated and an unavailable local tool.
  3. Check the bundled client version and HTTP/2 and HTTP/3 capabilities in the result.
  4. Run the TLS test as well. Compare individual measurements; saved runs can be reopened and exported to JSON, CSV and TXT.
curl --version

Limitations and checking results

Alt-Svc and HTTP/2 fallback do not prove HTTP/3. Actual HTTP/3 negotiation is required; blocked UDP can prevent the test.

DNSSEC is not validated. ICMP loss alone does not mean a server is down. Exports omit response bodies, cookies, authentication data and URL queries.

An Alpha development version is available. Before using it on important systems, review the limitations of individual features and prepare backups.

CH-J Server Manager – Actual diagnostics screen measuring a local HTTP test service; this example does not prove HTTP/3 support on a public server.
Actual diagnostics screen measuring a local HTTP test service; this example does not prove HTTP/3 support on a public server. Example of the Alpha interface. Appearance and control language may differ by version and settings. Open full size ↗
Download the applicationDetailed documentation →