Use this HTTP2 test to verify if your website support HTTP2 protocol, start now using our free online HTTP2 check tool:
Is HTTP2 enabled?
HTTP2 Check FAQ
About this HTTP2 Test Tool
Our HTTP2 test tool will help you to check if your website does support HTTP2 protocol or not. If not, you should consider moving from HTTP to HTTPS asap, you can read the full benefits of HTTP2 in the information below.
What is HTTP2?
For years, we all knew and used the famous HTTP/1.1 protocol that was introduced in 1997. Almost two decades after that, the HTTP protocol receives an update with the new HTTP2/0 protocol, showing some exciting new improvements over HTTP 1.1 in terms of performance and security for both clients and servers.
HTTP2 main features include: multiplexed parallel requests from a single TCP connection, uses HPACK header compression, ALPN extension is fully supported to allow fast-encrypted connections, allows domain sharding and also reduces rount trip times to make your website browsing experience even faster.
What Browsers do support HTTP2?
HTTP2 is currently supported by all major modern browsers like:
- Google Chrome
- Mozilla Firefox
- Microsoft Edge
- iOS Safari
- Android browser
- Chrome for Android
If you need an specific browser list you can get the full supported list from caniuse
Enable HTTP2 on your web server
We’ve written an useful tutorial that explains step by step how to enable http2 support for your websites, see the link below:
- Enable HTTP2 support on Apache and Nginx web servers
Is it possible to check for HTTP2 suppor from command line / terminal?
Sure, it’s easy to check for http2 support using the terminal on Linux and Unix systems, we have the all powerfull curl command that can help us:
Just use the curl –http2 parameter as you see below:
[firstname.lastname@example.org ~]$ curl --http2 https://nixcp.com -I HTTP/2 200 server: nginx date: Thu, 26 Oct 2017 13:23:50 GMT content-type: text/html; charset=UTF-8 vary: Accept-Encoding link: <https://nixcp.com/wp-json/>; rel="https://api.w.org/" strict-transport-security: max-age=15724800; includeSubdomains; preload x-frame-options: SAMEORIGIN x-content-type-options: nosniff x-xss-protection: 1; mode=block content-security-policy: default-src https: data: 'unsafe-inline' 'unsafe-eval'
If you get “HTTP/2 200” then you have HTTP2 working, otherwise you will get a “HTTP/1.1 200 OK” response.
Other useful resources: