HTTP3 Checker - Test Your Website for HTTP3 Support

Discover if your website is using the latest HTTP3 protocol for faster, more reliable connections

lps.go.id

check_circle QUIC is supported

check_circle HTTP/3 is supported

HTTP/3 Check established a QUIC connection for all attempts made with the given endpoint. The server is using HTTP/2. See the metrics below for more information.

0-RTT

Zero Round Trip Time Resumption (0-RTT)

The QUIC handshake for this connection was completed without any additional round-trips.

SUCCESS
h3

QUIC Versions

These are the QUIC versions supported by this QUIC endpoint.

AGREED SUPPORTED
Connection ID Packet RX Handshake Done
57cd2f2d... 1.70 6.84

HTTP/3 Server Information

HTTP Version: HTTP/2
Server: Sentinel
Status Code: 200
Response Time: 1272.36 ms

Response Headers

Header Value
date Sat, 25 Oct 2025 19:58:16 GMT
content-type text/html
vary Accept-Encoding
cache-control max-age=0, no-cache, no-store, must-revalidate
x-cache-location /konten/cache/all
accept-ranges bytes
set-cookie sl-session=LmIxbVh9/mhRliOOq78ZYg==; SameSite=Strict; Secure; Path=/; Max-Age=86400; HttpOnly
server Sentinel
permissions-policy autoplay=(self), camera=(self), fullscreen=(*), microphone=(self), payment=(self)
referrer-policy strict-origin-when-cross-origin
strict-transport-security max-age=31536000; includeSubDomains;
x-content-type-options nosniff
x-frame-options SAMEORIGIN
x-permitted-cross-domain-policies none
x-xss-protection 1; mode=block
x-download-options noopen
cross-origin-embedder-policy unsafe-none
cross-origin-opener-policy same-origin-allow-popups
cross-origin-resource-policy cross-origin
content-security-policy base-uri 'none'; default-src 'none'; script-src 'self' 'strict-dynamic' 'nonce-V4XuKxOOhJE2gX3wAsHuqRXngxKqVuON' 'wasm-unsafe-eval'; script-src-elem 'self' 'strict-dynamic' 'nonce-V4XuKxOOhJE2gX3wAsHuqRXngxKqVuON' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' blob: data: https://*.tile.openstreetmap.org https://maps.googleapis.com https://maps.gstatic.com https://www.gstatic.com https://www.googletagmanager.com; font-src 'self' data: https://fonts.gstatic.com https://widget-v4.tidiochat.com; media-src 'self'; connect-src 'self' wss: https://captcha.lps.go.id https://maps.googleapis.com https://www.google-analytics.com https://stats.addtoany.com; object-src 'none'; form-action 'self'; frame-ancestors 'self'; frame-src 'self' https://dashboard-datastatistik.lps.go.id https://docs.google.com https://static.addtoany.com https://view.officeapps.live.com https://www.google.com https://www.youtube.com; manifest-src 'self'; worker-src 'self' blob:; upgrade-insecure-requests;
alt-svc h3=":443"; ma=2592000, h3-29=":443"; ma=2592000

HTTP/3 Statistics

Zero Round Trip Time Resumption (0-RTT)

The QUIC handshake for this connection was completed without any additional round-trips.

SUCCESS

QUIC Versions

These are the QUIC versions supported by this QUIC endpoint.

AGREED SUPPORTED


Connection ID

This unique identifier for a QUIC connection is used to ensure that changes to an endpoint's lower network layer address (UDP/IP) does not affect the delivery of the QUIC connection's packets.

This tool attempts two connections to test the server's 0-RTT capabilities. During the first connection, the client receives important handshake material from the server. With 0-RTT, the client can start to send data immediately if it uses this handshake material when it creates the second connection.


Packet RX

This value represents the time between the first packet sent and the first packet received (measured in milliseconds).


Handshake Done

This value represents the time between when the first packet is sent and when the handshake is completed (measured in milliseconds).

Take notice of the difference in this metric between the first connection and the second connection. Using 0-RTT, future connections (i.e. the second connection) can complete the handshake much faster than the original connection.