Yes. The public check requires no account. A connected workspace is needed only for saved evidence, monitoring, and deeper workflows.

boltFree tool · no account required

Free HTTP/2 Test

Q: Does Novaverb estimate missing numbers?

No. Missing evidence produces an unavailable or incomplete state instead of an invented metric.

Q: What can I do after this free check?

Connect the target to a Novaverb workspace to save evidence, monitor changes, and run site-wide analysis.

Check whether a website supports HTTP/2 with a live TLS handshake. See ALPN support, the negotiated protocol, TLS version, and whether HTTP/3 is advertised — free, no account.

verifiedEvidence shown with sourcelock_openNo account requiredblockNo invented metrics

bolt

Run a real check above

Submit a public URL, domain, or keyword. Novaverb will show only the evidence this tool can actually retrieve or measure.

Evidence model

Know what the result proves

Each free check separates measured evidence from interpretation, and interpretation from the deeper work available in a connected workspace.

database

1. Source

Live TLS ALPN negotiation. The result identifies where its evidence came from.

rule

2. Boundary

This performs a live TLS handshake and reads the ALPN-negotiated protocol. HTTP/2 requires ALPN; HTTP/3 support is inferred from the Alt-Svc response header, not a QUIC handshake.

conversion_path

3. Next action

Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.

HTTP/2, ALPN & why they matter

HTTP/2 is a major revision of the HTTP protocol that lets a browser and server exchange many requests over a single connection at once (multiplexing), compress headers, and prioritise resources — cutting latency versus HTTP/1.1. In browsers, HTTP/2 is only used over HTTPS, and the protocol is chosen during the TLS handshake using an extension called ALPN (Application-Layer Protocol Negotiation). If the server does not advertise "h2" via ALPN, the browser falls back to HTTP/1.1.

How to enable HTTP/2

Use a modern web server: nginx 1.9.5+, Apache 2.4.17+ with mod_http2, LiteSpeed, or Caddy all support HTTP/2. Enable the http2 directive on your TLS listener.
Serve over HTTPS with a valid certificate: Browsers require TLS for HTTP/2, and ALPN needs OpenSSL 1.0.2 or newer on the server.
Put a CDN in front: Most CDNs terminate HTTP/2 (and often HTTP/3) at the edge, so you gain it even if your origin is older.

What this test proves

Live ALPN handshake

We open a real TLS connection, offer h2 and http/1.1, and report exactly which protocol the server selected.

HTTP/3 is read from Alt-Svc

HTTP/3 support is inferred from the Alt-Svc response header advertising an h3 endpoint, not a full QUIC handshake.

Common questions

HTTP/2 Test FAQ

Is this tool free?

Yes. You can run the public check without creating an account. A connected workspace is required only for saved evidence, monitoring, and deeper product workflows.

Where does the result come from?

Live TLS ALPN negotiation. This performs a live TLS handshake and reads the ALPN-negotiated protocol. HTTP/2 requires ALPN; HTTP/3 support is inferred from the Alt-Svc response header, not a QUIC handshake.

Does Novaverb estimate missing numbers?

No. If the required evidence is unavailable, the tool returns an unavailable or incomplete state instead of inventing a metric.

What can I do after this free check?

Connect the target to a Novaverb workspace to keep evidence, run site-wide analysis, monitor changes, and move findings into an accountable workflow.

More free checks