1. Quelle
Live TLS ALPN negotiation. The result identifies where its evidence came from.
Check whether your web server supports HTTP/2 via TLS ALPN negotiation. Verify protocol speed, cipher suites, and modern browser readiness.
Reichen Sie eine öffentliche URL, Domain oder ein Keyword ein. Novaverb zeigt nur die Beweise an, die dieses Tool tatsächlich abrufen oder messen kann.
This check proves whether a server actually negotiates HTTP/2 on a real connection, because the protocol is read from the TLS ALPN handshake rather than from any header that claims support. It also reports whether HTTP/3 is advertised. It does not measure speed: negotiating h2 says a connection is multiplexed, not that a page is fast.
Live TLS ALPN negotiation. The result identifies where its evidence came from.
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.
Verwende das Ergebnis, um ein Problem zu überprüfen, und verbinde dann einen Arbeitsbereich, wenn du Historie, Überwachung oder eine standortweite Analyse benötigst.
Dieser Checker öffnet eine Live-HTTPS-Verbindung, bietet h2 und http/1.1 über TLS ALPN an und berichtet dann das Protokoll, das vom Endpunkt ausgewählt wurde. Das macht das Urteil zum Protokollbeweis - nicht zu einem geschätzten Wert oder einer Browsersimulation.
Überprüfe das Zertifikat und den SNI-Hostnamen, die CDN- oder Load-Balancer-TLS-Richtlinie, die ALPN-Unterstützung im TLS-Stack und ob ein Proxy die Verbindung beendet, bevor sie deinen Ursprung erreicht.
Das ausgewählte ALPN-Protokoll bei einer frischen TLS-Verbindung, plus grundlegende Verbindungszeit und HTTP-Status.
Es garantiert keine schnelleren Seiten, HTTP/3-Verfügbarkeit, Browserunterstützung in jedem Netzwerk oder gute Core Web Vitals.
Dieser Test führt einen Live-TLS-Handshake durch und liest das ALPN-verhandelte Protokoll; HTTP/3-Unterstützung wird aus dem Alt-Svc-Header abgeleitet, nicht aus einem QUIC-Handshake.
Submit the domain or any URL on the site. Only the origin matters, so path and query are normalised away before the handshake. A private host is refused. A CDN in front of the origin answers this check, which is the honest answer for visitors, even when the origin behind it speaks a different protocol.
yourdomain.comJede Adressform funktioniert. http oder https, mit oder ohne www, eine nackte Domain oder ein vollständiger Pfad - wir normalisieren es für Sie. Wir testen den sicheren Ursprung in jedem Fall.https://www.yourdomain.com/pageEine vollständige URL mit einem Pfad ist in Ordnung - HTTP/2 ist eine Verbindungs-Eigenschaft, daher überprüfen wir den Ursprung dahinter.fast web hostingDas ist eine Suchphrase, keine Adresse - geben Sie eine Domain oder URL zum Testen ein.The input is normalised to the site's origin and a live TLS handshake is completed. The protocol is taken from the ALPN negotiation, so HTTP/2 is confirmed only when the server genuinely negotiates 'h2'. The Alt-Svc response header is read separately to note whether an HTTP/3 endpoint is advertised alongside it.
Two IETF specifications define this result. RFC 9113 defines HTTP/2 itself, and RFC 7301 defines Application-Layer Protocol Negotiation, the TLS extension this check reads to learn which protocol was actually agreed. Reading ALPN rather than a response header is what makes the answer a measurement instead of a claim.
Bestätigt die HTTP/2-Unterstützung so, wie es das Protokoll erfordert: über ALPN, nicht über eine Header-Aussage.
Spezifikation lesenLiest das ALPN-verhandelte Protokoll während des Live-TLS-Handshakes.
Spezifikation lesenIt performs a live TLS handshake and reads the ALPN-negotiated protocol to confirm whether your server actually serves HTTP/2. It also reports the TLS version and whether HTTP/3 is advertised via the Alt-Svc header.
HTTP/2 is a major revision of HTTP that multiplexes many requests over a single connection, adds header compression (HPACK), and enables prioritisation. It reduces round-trip overhead versus HTTP/1.1, speeding delivery of pages with many resources.
Over HTTPS, HTTP/2 is negotiated during the TLS handshake using ALPN (Application-Layer Protocol Negotiation). The client offers h2, and if the server agrees, the connection uses HTTP/2. This test reads exactly that ALPN result.
Enable the HTTP/2 module in your web server or CDN (for example the http2 directive in modern server builds) and ensure HTTPS with ALPN is active. HTTP/2 in browsers effectively requires TLS, so a valid certificate is prerequisite.
HTTP/1.1 sends requests largely one-at-a-time per connection and can suffer head-of-line blocking. HTTP/2 multiplexes concurrent streams over one connection and compresses headers, cutting latency for resource-heavy pages without opening many parallel connections.
No. HTTP/3 here is only inferred from the Alt-Svc response header, which advertises an h3 endpoint. This ALPN-based test confirms HTTP/2 directly but does not perform a QUIC handshake to prove HTTP/3 works.
The specification allows cleartext HTTP/2, but every major browser only supports it over TLS via ALPN. In practice you need a valid certificate and HTTPS for browsers to negotiate and use HTTP/2 at all.
TLS 1.3 is preferred for its faster handshake and stronger defaults, with TLS 1.2 as an acceptable minimum. HTTP/2's blocklist forbids obsolete ciphers, so modern TLS configuration avoids fallback to HTTP/1.1.
Confirm HTTPS with ALPN is enabled and the HTTP/2 module is on at whichever layer terminates TLS, often a CDN or reverse proxy rather than your origin. Some hosts serve HTTP/2 only at the edge.
Indirectly. HTTP/2 can improve real-world load speed by cutting connection overhead, which supports better Core Web Vitals and user experience, factors that influence rankings. It is a performance enabler, not a direct ranking signal by itself.