WORK FROM ANYWHERE / NETWORK TOOLS

Know your connection. Work with confidence.

Check your public IP, address exposure and connection quality.

Tests run in sequence so speed tests do not affect other results

Tests connect to third-party services only when you start them. Providers can see your public IP and test requests. Speed tests use up to about 22.5 MB of payload, plus protocol overhead. We do not read personal files or request location, camera or microphone access.How your data is used

IP address & location

This browser’s public internet exit

Not tested

View your public IP, approximate location, network operator and time zone.

Source Cloudflare / ipwho.is

Look up another public IP

DNS leak check

Observe the DNS resolvers handling your queries

Not tested

Find resolvers using unique test domains, without using the application server’s DNS results.

Compare the results with your expected VPN or secure DNS settings. Public DNS, browser DoH and VPNs may use different exits. Resolver count or country alone cannot establish a leak.

About this source

WebRTC leak check

Collect ICE candidates and compare with the current HTTP exit

Not tested

Check whether WebRTC exposes other addresses, without opening your camera or microphone.

Only evaluates evidence visible to this browser in this test

Speed & connection quality

Your browser measures its network path to Cloudflare

Not tested

Effective download rate—Mbps

Effective upload rate—Mbps

Idle HTTP latency—ms · median

Idle jitter—ms · consecutive valid samples

About 10–60 seconds, up to 90 seconds. Speed tests consume data; run them when needed.

Rates are short application-layer estimates that include HTTP and browser overhead. Latency is not ICMP ping. HTTP failure rate is not UDP packet loss. Load latency shows “—” when the load is too brief to measure.

Up to about 22.5 MB payload · Stop at any time