IPNixa / NETWORK TOOLS

TLS & HTTP Version Check: HTTP/3, QUIC and RTT

See the TLS version, cipher and HTTP protocol this browser uses with IPNixa. Read edge-reported TCP or QUIC RTT with missing values and inapplicable protocols clearly labeled.

NIXA / CONNECTION REPORT

Inspect your connection.

Run a fresh check from this browser.

Ready when you are. Results remain on this page.

Results describe requests to IPNixa from this browser. No scan history is stored by this tool.

04 / TRANSPORTREADY

Secure transport

TLS, HTTP protocol and the edge handling this request.

Status: Not tested

How to read this result →

FROM RESULT TO NEXT STEP

Understand TLS, HTTP/3 and RTT

The protocol and RTT describe the browser-to-edge inspection request. They help explain which transport was used and which measurements apply.

Why is TCP not used with HTTP/3?

HTTP/3 uses QUIC. IPNixa marks TCP RTT as inapplicable and shows QUIC RTT when the edge reports it, rather than presenting a misleading TCP zero.

Understand HTTP/3 and 0 ms labels Inspect my transport

Does a missing or zero RTT mean no delay?

No. Not reported means the timing was unavailable. A reported zero retains a precision caveat; browser connection reuse is identified separately in resource timing.

Interpret missing and reused timings Measure HTTP response time

How to use this check

Open this page in the browser and network you want to inspect, then select Run check.
Read the transport fields and their source. An unavailable value means the server did not report it.
If you change VPN or network, run the check again. These results describe the new request, not every app or website.

What this check measures

This reads the connection between your browser and the Cloudflare edge serving IPNixa. HTTP/3 uses QUIC, so TCP RTT is marked not used. Missing edge values remain not reported; a reported zero keeps a precision caveat. These are separate from browser connection-setup timings. This does not scan another website, validate its certificate chain or audit your whole device. TLS protects data in transit; it does not establish that a website is trustworthy.

Why is TLS unavailable locally?

Local HTTP previews do not negotiate TLS with a public Cloudflare edge. We show unavailable fields instead of simulated security results.