Skip to main content

HTTP Version

free
GET/v1/domain/http-version

Tests which HTTP protocol versions a domain supports including HTTP/1.1, HTTP/2 (RFC 9113), and HTTP/3 (RFC 9114, built on QUIC/RFC 9000). Modern HTTP versions significantly improve performance through multiplexing and reduced latency.

What It Does

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

Why It's Useful

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

Use Cases

Performance Engineer

Performance Audit

Verify HTTP/2 or HTTP/3 is enabled for optimal content delivery.

Ensure modern protocols are configured for best performance.

DevOps Engineer

Infrastructure Assessment

Confirm load balancers and CDNs support modern HTTP protocols.

Validate infrastructure supports latest protocol standards.

Technical SEO

Competitive Benchmark

Compare HTTP protocol support across competitor sites.

Identify protocol optimization opportunities versus competitors.

Parameters

NameTypeRequiredDescription
domainstringRequiredThe domain to check HTTP version support forExample: google.com

Response Fields

FieldTypeDescription
domainstringThe queried domain
http11booleanHTTP/1.1 support
http2booleanHTTP/2 support (inferred for HTTPS connections)
http2ConfidencestringConfidence level: "confirmed" if HTTP/3 detected (implies HTTP/2), "inferred" otherwise
http3booleanHTTP/3 (QUIC) support detected via Alt-Svc header
protocolstringDetected protocol name
versionstringDetected protocol version
altSvcstringRaw Alt-Svc header value
altSvcEntriesarrayParsed Alt-Svc entries with protocol, authority, and max-age
recommendationsarrayProtocol optimization suggestions

Code Examples

cURL
curl "https://api.edgedns.dev/v1/domain/http-version" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "domain=google.com"
JavaScript
const response = await fetch(
  'https://api.edgedns.dev/v1/domain/http-version?domain=google.com',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

const data = await response.json();
console.log(data);
Python
import requests

response = requests.get(
    'https://api.edgedns.dev/v1/domain/http-version',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'domain': 'google.com'
    }
)

data = response.json()
print(data)

Read the full HTTP Version guide

Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.

Read the guide →

Related Endpoints

External References

Learn more about the standards and protocols behind this endpoint.

Try This Endpoint

Test the HTTP Version endpoint live in the playground.