Latency
Measure HTTP reachability and round-trip timing to regional endpoints (browser-safe techniques).
Test configuration
Regions
Tip: choose Custom and paste a list like name,https://host/ — one per line.
Custom region list
We’ll issue no-cors fetches (or image loads) and measure timing. The endpoint must be publicly reachable.
Browsers can’t send ICMP pings. This tool measures HTTP(S) reachability and timing using safe client-only methods.
Results
| Region | Host | Min | P50 | P90 | Avg | Max | Jitter | Samples |
|---|---|---|---|---|---|---|---|---|
| No results yet. | ||||||||
Raw log
DNS over HTTPS
Resolve hostnames using popular DoH resolvers, directly from your browser.
Query
Some networks block DoH endpoints. If you see errors, try a different resolver.
Answer
| Type | Data | TTL | Latency |
|---|---|---|---|
| No results yet. | |||
Response JSON
IP & Network
Quick visibility into your public IP and WebRTC connectivity details.
Public IP
Public IP
Loading…
Lookup source
ipify.org
Notes
System DNS servers aren’t directly readable in browsers. Use the DoH tool above to compare resolvers.
WebRTC Connectivity (STUN)
If you don’t see srflx candidates, your network may block UDP/STUN or WebRTC is restricted.
About
A lightweight, static page for endpoint-accurate checks. No backend required.
- Client-only: everything runs in your browser; no API keys.
- Latency: measures HTTP reachability and timing via fetch (no-cors) with optional image fallback.
- DNS: uses standard DoH JSON endpoints (Google / Cloudflare / Quad9).
- Network: public IP via ipify; WebRTC ICE candidates via STUN.
Build: