Developer Network Toolkit
Measure DNS resolution, TLS handshake, TCP connect, TTFB, WebSocket latency, and HTTP/3 support against major endpoints. Free network diagnostics for developers.
DNS Resolution
4.42 ms
TLS Handshake
29.55 ms
TCP Connect
6.54 ms
TTFB
106.11 ms
HTTP/3
Yes
WebSocket
Client-side
DNS Resolution
Time to resolve hostnames to IP addresses.
| Host | Time | Addresses |
|---|---|---|
| www.google.com | 1.7 ms | 142.251.155.119, 142.251.154.119, 142.251.152.119, 142.251.153.119, 142.251.156.119, 142.251.157.119, 142.251.150.119, 142.251.151.119 |
| www.cloudflare.com | 0.95 ms | 104.16.124.96, 104.16.123.96 |
| www.amazon.com | 1.61 ms | 3.170.24.177 |
| speed.cloudflare.com | 4.46 ms | 162.159.140.220, 172.66.0.218 |
| checkspeedpro.com | 13.39 ms | 216.198.79.1 |
TLS Handshake
Time to complete TLS handshake (HTTPS setup).
| Host | Port | Time |
|---|---|---|
| www.google.com | 443 | 22.8 ms |
| www.cloudflare.com | 443 | 11.16 ms |
| speed.cloudflare.com | 443 | 11.72 ms |
| checkspeedpro.com | 443 | 72.53 ms |
TCP Connect
Time to establish a TCP connection.
| Host | Port | Time |
|---|---|---|
| www.google.com | 443 | 11.77 ms |
| www.cloudflare.com | 443 | 3.51 ms |
| speed.cloudflare.com | 443 | 5.56 ms |
| checkspeedpro.com | 443 | 14.71 ms |
| 1.1.1.1 | 53 | 1.62 ms |
| 8.8.8.8 | 53 | 2.1 ms |
Time to First Byte
Time from request to first byte of response.
| URL | Time | Status |
|---|---|---|
| https://www.google.com/ | 46.42 ms | 200 |
| https://www.cloudflare.com/ | 77.7 ms | 200 |
| https://speed.cloudflare.com/ | 62.41 ms | 200 |
| https://checkspeedpro.com/ | 237.92 ms | 200 |
HTTP/3 Support
Whether the origin supports HTTP/3 (QUIC), detected via Alt-Svc header.
| URL | HTTP/3 | Alt-Svc |
|---|---|---|
| https://www.google.com/ | Yes | h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 |
| https://www.cloudflare.com/ | Yes | h3=":443"; ma=86400 |
| https://speed.cloudflare.com/ | No | — |
| https://checkspeedpro.com/ | No | — |
WebSocket Latency
Round-trip latency over a WebSocket connection (measured in browser).
WebSocket latency is measured client-side. Open your browser's DevTools → Network tab and connect to:
wss://checkspeedpro.com/api/network/websocketSend a ping message and measure the round-trip time for the echo response.