HTTP Version: a beginner's guide

HTTP (HyperText Transfer Protocol) is the protocol every web browser uses to talk to every web server. It has gone through four major versions: HTTP/1.0 (1996, mostly historical), HTTP/1.1 (1997, the workhorse for two decades), HTTP/2 (2015, a major rewrite), and HTTP/3 (2022, an even bigger one). Each version is faster than the last, and each was rolled out across the internet over the course of a few years after its standardization. The interesting fact is that the speed improvements are essentially free for any site that opts in — the browser does all the hard work, and the server just has to enable the new version.

You should care because most of the performance gain from upgrading HTTP versions is invisible until you stop and measure it. HTTP/1.1 sends one request at a time per connection, with all the overhead of opening and closing TCP connections constantly. HTTP/2 sends multiple requests in parallel over a single connection, which saves enormous amounts of round-trip time. HTTP/3 goes further by replacing TCP with QUIC, a new transport protocol that handles connection setup, encryption, and multiplexing in a single step — and continues to work even if you switch networks (Wi-Fi to cellular) mid-page-load. The cumulative gain from /1.1 to /3 on a typical page is often 20–40% faster, with zero changes to the HTML.

The four things every HTTP version check looks at:

• Which version is the server actually negotiating? A server can support multiple versions; the client and server pick the highest both support.

• Is HTTP/2 enabled? HTTP/2 is the floor for any modern site. There is no good reason to be on HTTP/1.1 in 2025.

• Is HTTP/3 enabled? HTTP/3 is opt-in and requires `Alt-Svc` headers or other discovery mechanisms; it is not yet automatic.

• Are protocol-specific optimizations turned on? HTTP/2 has features like server push and header compression; HTTP/3 has 0-RTT connection resumption. Both need to be configured.

Three questions an HTTP version check answers:

• What HTTP version is my site actually serving to real visitors?

• Should I be on HTTP/3 yet, and what would it take to enable it?

• Are there any clients still negotiating down to HTTP/1.1 — and if so, why?

The cost of staying on old HTTP versions is the slow performance gap between you and competitors who upgraded. The fix is usually one configuration line on a modern web server or CDN — Cloudflare, Fastly, Vercel, and most others enable HTTP/2 and HTTP/3 by default. The protocols are documented in RFC 9112 (HTTP/1.1), RFC 9113 (HTTP/2), and RFC 9114 (HTTP/3).

In one sentence: Check HTTP/2 and HTTP/3 support

Tests which HTTP (HyperText Transfer Protocol) protocol versions a domain supports including HTTP/1.1, HTTP/2 (the official internet standard), and HTTP/3 (the official internet standard, built on QUIC/the official internet standard). Modern HTTP versions significantly improve performance through multiplexing and reduced latency.

Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.

Here's what's actually happening behind the scenes when you call this endpoint:

Checks HTTP/3 support by parsing the Alt-Svc response header. Infers HTTP/2 support for HTTPS (secure HyperText Transfer Protocol) connections (Cloudflare Workers cannot verify ALPN negotiation directly). Reports the detected protocol version and identifies available upgrade paths.

If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.

Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the HTTP Version tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.

HTTP/2 (the official internet standard) and HTTP/3 (the official internet standard) provide significant performance improvements through multiplexing, header compression (HPACK/QPACK), and 0-RTT connection establishment. HTTP/3 over QUIC (the official internet standard) eliminates head-of-line blocking at the transport layer. Verifying support is important for performance optimization and ensuring CDN/load balancer configuration is correct.

Picture this in real life. Imagine a performance engineer. Here's the situation they're walking into: Verify HTTP/2 or HTTP/3 is enabled for optimal content delivery. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the HTTP Version tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.

Three questions this tool answers in plain English. If any of these have ever crossed your mind, the HTTP Version tool is built for you:

• Why does my website feel slow on real devices, even though it looks fine on mine?

• Which specific change would give me the biggest speed boost for the least work?

• Am I losing visitors and search rankings because of performance problems I cannot see?

You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.

Who gets the most out of this. Founders watching their conversion rates, marketers trying to lift landing-page revenue, ecommerce operators chasing every percentage point of speed, and developers tuning Core Web Vitals. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.

What happens if you skip this entirely. Skip it and visitors bounce, conversions drop, and your search ranking quietly slides — all from a problem nobody on the team can see. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.

If you're still on the fence about whether the HTTP Version tool belongs in your toolbox, this section is for you. Below you'll meet three real people — a performance engineer, a devops engineer, and a technical SEO — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.

Story 1: Performance Audit

Imagine you're a performance engineer. Verify HTTP/2 or HTTP/3 is enabled for optimal content delivery.

Why it matters: Ensure modern protocols are configured for best performance.

Story 2: Infrastructure Assessment

Imagine you're a devops engineer. Confirm load balancers and CDNs support modern HTTP (HyperText Transfer Protocol) protocols.

Why it matters: Validate infrastructure supports latest protocol standards.

Story 3: Competitive Benchmark

Imagine you're a technical SEO. Compare HTTP (HyperText Transfer Protocol) protocol support across competitor sites.

Why it matters: Identify protocol optimization opportunities versus competitors.

Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the HTTP Version tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:

• Before a high-traffic marketing campaign or product launch.

• After a redesign, to make sure performance did not regress.

• When your conversion rate drops without an obvious cause.

• On a recurring schedule, to enforce a performance budget for your team.

If you can see yourself in even one of those bullets, the HTTP Version tool will pay for itself the first time you use it.

Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the HTTP Version tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.

If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:

"Use the HTTP Version tool to check google.com and explain anything that looks wrong in plain language."

The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.

If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.

There's just one piece of information you need to provide. The table below explains exactly what it is and what a real value looks like.

When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.

These tools pair naturally with HTTP Version. If you're already running this check, the related ones often answer the next question that comes up:

• Compression Check — Analyze gzip/brotli/zstd compression support

• Response Time — Measure server response latency

• Cache Headers — Analyze caching configuration

If you're using an AI assistant through MCP (Model Context Protocol), you can ask it to run several of these in one go: "Check HTTP Version and the related tools for example.com and tell me what looks off."

If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.

CDN (Content Delivery Network) — A worldwide network of servers that store copies of your website close to your visitors so pages load fast.

HTTP (HyperText Transfer Protocol) — The language web browsers and websites use to talk to each other.

HTTPS (secure HyperText Transfer Protocol) — HTTP with encryption — the little padlock in your browser. It means nobody between you and the website can read what you're sending.

RFC (Request for Comments) — The official internet standards documents. When someone says 'RFC 8484' they mean a specific numbered standards document — in that case, the one defining DNS over HTTPS.